Quandoo Restaurant Booking API
★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontapiKey24 EndpointsREST
For Agents
Programmatically get customer data, get customer reservations. Covers 24 operations with apiKey authentication.
Use for: I need to customer data, I want to customer reservations, Search for allows to get merchant information by parameters, Find all allows to get a merchant by id
Not supported: Does not handle payments, communications, or crm — use for e-commerce only.
API for managing restaurant bookings, customers, merchants, reservations, and reviews. Allows partners to search restaurants, make reservations, manage customer data, handle reservation enquiries, and process reviews. Includes features for credit card verification, merchant availability checking, and reservation status management. The API exposes 24 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Quandoo Restaurant Booking API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Quandoo Restaurant Booking API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Quandoo Restaurant Booking API.
Get customer Data
Allows to get merchant information by parameters
Access Quandoo Restaurant Booking API e commerce resources via REST API
Use Cases
Patterns agents use Quandoo Restaurant Booking API for, with concrete tasks.
★ E-Commerce Operations
Use the Quandoo Restaurant Booking API to perform e commerce operations programmatically. The API provides 24 endpoints covering core functionality including get customer data, get customer reservations, allows to get merchant information by parameters.
Call GET /v1/customers/{customerId} to get customer data
Automated status Management
Automate status operations by combining multiple Quandoo Restaurant Booking API endpoints. Agents can get customer reservations and then allows to get merchant information by parameters in a single workflow.
Call GET /v1/customers/{customerId}/reservations to get customer reservations, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Quandoo Restaurant Booking API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'get customer data', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
24 endpoints — api for managing restaurant bookings, customers, merchants, reservations, and reviews.
METHOD
PATH
DESCRIPTION
GET
/v1/customers/{customerId}
Get customer Data
GET
/v1/customers/{customerId}/reservations
Get customer reservations
GET
/v1/merchants
Allows to get merchant information by parameters
GET
/v1/merchants/{merchantId}
Allows to get a merchant by id
GET
/v1/merchants/{merchantId}/availabilities
Get merchant availability days
GET
/v1/merchants/{merchantId}/availabilities/{date}/times
Get merchant availability time slots
GET
/v1/merchants/{merchantId}/customers
Get a list of Customers of a merchant
GET
/v1/merchants/{merchantId}/reservation-settings
Get merchant reservation settings
GET
/v1/customers/{customerId}
Get customer Data
GET
/v1/customers/{customerId}/reservations
Get customer reservations
GET
/v1/merchants
Allows to get merchant information by parameters
GET
/v1/merchants/{merchantId}
Allows to get a merchant by id
GET
/v1/merchants/{merchantId}/availabilities
Get merchant availability days
GET
/v1/merchants/{merchantId}/availabilities/{date}/times
Get merchant availability time slots
GET
/v1/merchants/{merchantId}/customers
Get a list of Customers of a merchant
GET
/v1/merchants/{merchantId}/reservation-settings
Get merchant reservation settings
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Quandoo Restaurant Booking API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'get customer data') and Jentic returns the matching Quandoo Restaurant Booking API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Quandoo Restaurant Booking API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
FAQs
Specific to using Quandoo Restaurant Booking API through Jentic.
What authentication does the Quandoo Restaurant Booking API use?
The Quandoo Restaurant Booking API uses an API key passed in the `X-Quandoo-AuthToken` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I get customer data with the Quandoo Restaurant Booking API?
Yes. Use the GET /v1/customers/{customerId} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Quandoo Restaurant Booking API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get customer data through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get customer data'. Jentic returns the matching Quandoo Restaurant Booking API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Quandoo Restaurant Booking API have?
The Quandoo Restaurant Booking API exposes 24 endpoints covering status, customers, merchants operations.
GET STARTED