Partner API
Jul 14, 2026 4:05 PM

Partner reservations

Partner reservations: working with bookings by the application identifier appId — retrieving and managing your own reservations.

If you are a partner application, you have an appId. With it you can retrieve all reservations created through your application, across all restaurants it is connected to.

Partner application reservations

GET /api/rsv/partner/{appId}/reservations

Returns the list of reservations created through the given partner application. appId defines the scope: only reservations from this partner’s restaurants are returned.

Parameters

ParameterInTypeDefaultDescription
appId *pathstring—Partner application identifier. Defines the scope — only reservations of this partner’s restaurants
approvalRequiredquerybooleantruetrue — only reservations that require approval; false — all reservations regardless of whether approval is needed
pendingOnlyquerybooleantruetrue — only pending reservations; false — reservations in any status
fromquerydate-time—Period start. If omitted — no lower bound
toquerydate-time—Period end. If omitted — no upper bound

Mind the defaults. By default approvalRequired=true and pendingOnly=true — that is, without parameters you get only reservations awaiting approval. To get all of the application’s reservations, pass approvalRequired=false&pendingOnly=false.

Examples

Only those awaiting approval (the default behavior):

Terminal window
curl "https://api.hostmeapp.com/api/rsv/partner/APP_ID/reservations" \
  -H "Authorization: Bearer $TOKEN"

All of the application’s reservations for a period:

Terminal window
curl -G "https://api.hostmeapp.com/api/rsv/partner/APP_ID/reservations" \
  -H "Authorization: Bearer $TOKEN" \
  --data-urlencode "approvalRequired=false" \
  --data-urlencode "pendingOnly=false" \
  --data-urlencode "from=2026-07-01T00:00:00" \
  --data-urlencode "to=2026-07-31T23:59:59"

Marking the source

To tell your own reservations apart in the restaurant’s general list (GET .../reservations), set on creation:

  • source — a human-readable source (for example, partner-widget);
  • VendorAppId — when working under a Vendor token it is set automatically and is available as a filter in the restaurant’s reservation list.

See Create and manage and Authentication → token types.