TheFork
TheFork is a leading European restaurant reservations marketplace, part of Tripadvisor, connecting diners with tens of thousands of restaurants across Europe and beyond. Through its developers portal, TheFork exposes a public REST API surface for restaurants, point-of-sale systems, and third-party partners to integrate with TheFork Management platform. The API enables partners to build custom booking flows, create and manage reservations with full detail such as meal date, party size, and customer data, surface preset menus and curated dining experiences, and access personalized guest data including allergies, dietary restrictions, and seating preferences. Offerings include a B2B API for restaurants and a POS API for point-of-sale providers.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles TheFork the way a machine reads it — 58 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — TheFork scores 60.1/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile TheFork
Each block below is one kind of artifact we hold for TheFork. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
TheFork Customers API
Look up customer and guest profile data.
TheFork Orders API
Open and close point-of-sale orders tied to reservations.
TheFork Reservations API
Create, retrieve, and update reservations.
TheFork Reviews API
Retrieve guest review details.
Open Collections 2
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
TheFork B2B API
OPEN COLLECTIONTheFork POS API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Thefork Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Thefork Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Custom Booking Funnel
Build a custom booking flow with real-time availability, offers, and preset menus, then create reservations directly against a restaurant.
Reservation Management
Create, retrieve, and update reservations including meal date, party size, and customer data.
Guest Profiles
Access personalized guest data such as allergies, intolerances, dietary restrictions, and seating preferences.
Customer Lookup
Find customer details by phone number for a given restaurant.
Reviews
Retrieve guest review details by review UUID.
Asynchronous Data Sync
Synchronize data without requiring real-time updates, using webhooks for reservation created and updated events.
POS Order Sync
Open and close point-of-sale orders tied to reservations and sync final amounts back to TheFork Management.
Scroll within the panel for all 7 ·
Semantic Vocabularies 3
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
TheFork API Rules
SPECTRALTheFork API Rules
SPECTRALJSON Schema 15
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CustomerInput
JSON SCHEMACustomer
JSON SCHEMAOffer
JSON SCHEMAReservationCreateRequest
JSON SCHEMAReservation
JSON SCHEMAReservationStatus
JSON SCHEMAReservationUpdateRequest
JSON SCHEMAReview
JSON SCHEMACustomer
JSON SCHEMAMoney
JSON SCHEMAOffer
JSON SCHEMAOrderClose
JSON SCHEMAOrder
JSON SCHEMAReservationStatus
JSON SCHEMATable
JSON SCHEMAScroll within the panel for all 15 ·
JSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Thefork B2B Reservation Structure
JSON STRUCTUREThefork Pos Order Structure
JSON STRUCTUREExamples 5
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Restaurant Booking Integration
Restaurants and groups embed TheFork availability and booking into their own websites and apps.
POS Integration
Point-of-sale vendors connect their systems to reflect seated guests, open tickets, and reconcile spend with reservations.
Guest Personalization
Use allergy, dietary, and seating preferences to personalize the dining experience and pre-service preparation.
Review Aggregation
Pull guest reviews into restaurant CRM and reputation tooling.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
TheFork Management (TFM)
The restaurant management platform the APIs synchronize with.
Tripadvisor
Parent company; TheFork is part of the Tripadvisor group.
Auth0
Identity provider issuing OAuth 2.0 client credentials tokens.
Kong
API gateway fronting the public API with auth, rate limiting, and IP allowlisting.
Solutions 3
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
For Restaurants
B2B API for restaurants and groups to manage bookings and guests.
For POS Providers
POS API for point-of-sale vendors to sync orders and reservations.
For Partners
Partner API for third-party partners (announced as available soon).
Resources
Every other property we hold for TheFork — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/thefork · machine-readable index on apis.io