Get booking profile
Whether a granted location accepts partner bookings right now, which provider serves it, the capability set its provider declares (hold release, venue verbs, time-window listing, live floor), and the hold TTL. Read this before calling any other bookings endpoint: enabled: false means the location is not bookable through the Developer API yet, and a false capability is what the matching verb answers with capability_unsupported. Requires bookings:read.
Authorizations
API key — mpk_test_… for the sandbox, mpk_live_… for production. Issued by Maple during partner onboarding.
Path Parameters
Response
Success
booking_profile True when read with a live credential; test credentials only ever see test-mode data.
True when this location accepts partner bookings through the Developer API right now. When false, every other bookings endpoint for the location returns bookings_not_enabled.
The provider behind the location’s booking connection, or null when none is configured.
maple, opentable, resy, sevenrooms Windows when the location takes no reservations, in start order (walk-ins and waitlist seating are unaffected). Availability omits slots inside them. A quote taken before a window was added is refused when held, booked, or used for a change: 409 slot_unavailable at Maple-native locations, whose engine also withholds seatings that would run into a window, and 422 date_blocked at provider-managed ones.
The revision of blackout_dates. Send it as expected_revision to PUT /booking_blackouts so the write is refused (409 stale_blackout_dates) if the venue changed the list since you read it.
How long a hold taken through POST /booking_holds claims capacity before it expires, when Maple enforces the hold lifetime. Null when the location’s provider owns hold expiry (read expires_at on each hold) or no provider is configured.