Reservation Availability Update

post

https://api.yelp.com/v3/private/reservation_availability/update

Push reservation availability data for a venue. Each request contains slot data for one business across one or more dates.

Key concepts:

Per-date full replacement: Each date you send replaces everything Yelp has for that date. No diffs or patches.
Include booked slots: Send spots_open: 0 for fully-booked time slots so Yelp can distinguish "sold out" from "closed."
15-minute resolution: Slot times must be on 15-minute boundaries (HH:00, HH:15, HH:30, HH:45).
Timezone derived from venue: Yelp determines timezone from the business address. Times in the payload are local to the venue.
Validation is per request: If any date fails validation, the whole request is rejected with 400 and nothing is written. Fix the payload and resend.
Per-date results: A 200 response reports a status for each date. A date with status: error failed on Yelp's side after validation; retry that date.

Prerequisites:

The venue must be registered via the Data Ingestion API with service_type_v2 configuration.
The partner_business_id must match the ID used during DI onboarding.

Authentication: Bearer token via OAuth 2.0 client credentials. Your API key must be whitelisted for this endpoint and linked to a partner ID. Contact your Yelp partner integration representative.

Rate limits: 50 QPS per partner.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Availability data for one business

partner_business_id

string

required

Unique identifier for the venue in the partner's system (e.g., restaurant ID). Must match the ID used during DI onboarding.

service

string

Defaults to default

Service identifier. Use "default" for standard dining. Only the default service is indexed in search today; pushes for other services are accepted but not yet used.

pre_booking_notes

string | null

Notes displayed to diners during the booking flow (e.g., dress code, parking info).

seating_areas

array of objects

Optional. Omit to use the seating areas registered during DI onboarding. If sent, openings may only reference the areas listed here.

seating_areas

dates

array of objects

required

length between 1 and 90

Availability for one or more dates. Each date replaces all previously sent data for that date (per-date full replacement).

dates*

date

required

Calendar date in YYYY-MM-DD format. Must be today or in the future (up to +90 days).

party_sizes

array of objects

required

Availability grouped by party size. Include all party sizes that have availability for this date. Each party_size may appear once per date. Send an empty array to clear the date.

party_sizes*

Responses

`message` describes the first problem found.

code	description
UNAUTHORIZED_API_KEY	The API key provided is not currently able to query this endpoint.
TOKEN_INVALID	Invalid API key or authorization header.

200Availability accepted (per-date results)

400Invalid request payload. The whole request is rejected; message describes the first problem found.

401The API key has either expired or doesn't have the required scopes to query this endpoint. codedescriptionUNAUTHORIZED_API_KEYThe API key provided is not currently able to query this endpoint.TOKEN_INVALIDInvalid API key or authorization header.

403Partner API endpoints require set up by Yelp before they can be used. You are trying to access a Partner API endpoint for which your API Client has not been enabled. Please reach out to [email protected] for more information.

404Partner business not found

429You have either exceeded your daily quota, or have exceeded the queries-per-second limit for this endpoint. Try reducing the rate at which you make queries.

500Failed to process availability update

504Upstream timeout

`message` describes the first problem found.