Informations
- OpenAPI version:
3.0.3
Overview
Partner REST API reference v1
Section titled “Partner REST API reference v1”The Barestho Partner API allows third-party partners to manage restaurants, reservations, and webhook integrations on behalf of their customers.
All endpoints are scoped under /api/v1/partnership/ and require partner-level authentication. Partners can list and inspect the restaurants they have access to, create and manage table reservations on behalf of those restaurants, and subscribe to real-time events via webhooks.
Base URL: https://public.api.barestho.com/
Versioning: The current stable version is v1. Breaking changes will result in a new version prefix.
Authentication: All endpoints require HTTP Basic Authentication. Credentials are formed by concatenating your partner UUID and API token separated by a colon (uuid:api_token), then Base64-encoding the result.
Authorization: Basic Base64(uuid:api_token)
Your UUID and API token are provided during partner onboarding. Keep them secret and never expose them in client-side code or public repositories.
Authentication
Section titled “ Authentication ”basicAuth
Section titled “basicAuth ”HTTP Basic Authentication using your partner credentials.
The Authorization header must contain the word Basic followed by a Base64-encoded string built from your UUID and API token separated by a colon:
Authorization: Basic Base64(uuid:api_token)
Example — for UUID 550e8400-e29b-41d4-a716-446655440000 and token api_sec_1234:
# Base64-encoded NTUwZTg0MDAtZTI5Yi00MWQ0LWE3MTYtNDQ2NjU1NDQwMDAwOmFwaV9zZWNfMTIzNA==
# Final header Authorization: Basic NTUwZTg0MDAtZTI5Yi00MWQ0LWE3MTYtNDQ2NjU1NDQwMDAwOmFwaV9zZWNfMTIzNA== ```
Both credentials are provided during partner onboarding. Treat them as secrets and rotate your API token immediately if it is compromised (see the webhook auth-token endpoints for a comparable token rotation pattern).Security scheme type: http