canonical: https://jentic.com/apis/quandoo.com/quandoo

# Quandoo Restaurant Booking API

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.

## For AI agents

Programmatically get customer data, get customer reservations. Covers 24 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Get customer Data
- Allows to get merchant information by parameters
- Access Quandoo Restaurant Booking API e commerce resources via REST API

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'get customer data', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **status** — Operations related to status
- **customers** — Operations related to customers
- **merchants** — Operations related to merchants
- **reservation-enquiries** — Operations related to reservation-enquiries
- **availabilities** — Operations related to availabilities

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 53 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 61 / 100
  - Developer Experience & Jentic Compatibility: 68 / 100
  - AI-Readiness & Agent Experience: 31 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 79 / 100
- **View full report:** https://jentic.com/apis/quandoo.com/quandoo/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Quandoo Restaurant Booking API by hand means setting its X-Quandoo-AuthToken header on every call to api.quandoo.com and handling the merchant and reservation responses yourself. Through Jentic you install once, import the Quandoo Restaurant Booking API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Quandoo puts the merchant and customer id in the URL path (`/merchants/{merchantId}`, `/customers/{customerId}`), so a rule can pin your agent to one merchant: it can read that merchant's availabilities, customers, and reservation settings and nothing else. You choose the operations it may call, so it reads only the resources you allow.
- **Credential handling:** Your Quandoo auth token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get merchant availabilities' or 'read a customer's reservations', and Jentic returns the matching Quandoo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the Quandoo Restaurant Booking API?

Yes. Because you run Jentic One yourself, your own rules decide which Quandoo operations and credentials the agent may use. Quandoo puts the merchant and customer id in the URL path, so a rule can pin your agent to a single merchant and let it read only that merchant's availabilities, customers, and reservation settings. You choose the exact operations it may call, such as GET `/v1/merchants/{merchantId}/availabilities` or GET `/v1/customers/{customerId}/reservations`, and it reaches nothing you have not allowed.