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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fquandoo.com%2Fquandoo" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fquandoo.com%2Fquandoo" | sh
jentic register       # connects your agent to your Jentic One instance

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

GET STARTED

Start building with Quandoo Restaurant Booking API

Explore with Jentic One

View OpenAPI Document

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

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

Quandoo Restaurant Booking API

Name: Quandoo Restaurant Booking API
Brand: Quandoo Restaurant Booking API
Availability: InStock

AI ReadinessFoundational (C-)53/100

See full scorecard

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

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4

85%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

69%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

63%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Quandoo Restaurant Booking API to your agent

Capabilities

Use Cases

Start building with Quandoo Restaurant Booking API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Quandoo Restaurant Booking API

Jentic AI Readiness Score

Quandoo Restaurant Booking API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness