Cooperto It API Cooperto.it
★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingbearer38 EndpointsREST
For Agents
Manage restaurant reservations, walk-in queues, fidelity card holders and contact lists for venues running on the Cooperto.it platform.
Use for: I need to add a walk-in to the restaurant queue with the customer's phone number, Confirm a customer has arrived for their queue position, Remove a queue entry because the party left, Look up a contact by email in the Cooperto venue CRM
Not supported: Does not handle payments, kitchen ticketing, or POS orders — use for reservations, walk-in queues and venue contact records only.
Jentic publishes the only available OpenAPI specification for API Cooperto.it, keeping it validated and agent-ready. Cooperto is an Italian restaurant operations platform with REST APIs for reservations, queue management, contact records, fidelity cards and WiFi login flows. The 38 endpoints cover creating and confirming queue entries, listing reservations by venue, retrieving contact details by email or code, and triggering manual marketing automations on a queue item. Authentication is bearer token, scoped to a single locale (restaurant) account, and request and response payloads use Italian field names that map to Cooperto's internal data model.
Install Jentic One Beta
Connect the API Cooperto.it to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Cooperto.it, 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 API Cooperto.it API.
Create a queue entry for a walk-in customer with name, email or phone
Confirm a customer's arrival from a queue and remove them when seated
List the live queue for an authenticated venue and get details by queue code
Retrieve contact details by email address or contact code from the venue's CRM
Trigger pre-defined manual marketing automations against a specific queue entry
Pull the fidelity card roster and reservation list for a Cooperto venue
Use Cases
Patterns agents use API Cooperto.it API for, with concrete tasks.
★ Restaurant Walk-in Queue Management
Front-of-house staff and host-stand tablets can use the Coda endpoints to add walk-ins, confirm arrivals and clear seated parties from the queue. The API returns the queue code which can be SMSed to the customer and used later to look up their position. Operations like POST /api/Coda/Crea, POST /api/Coda/ConfermaArrivo and POST /api/Coda/Elimina cover the full walk-in lifecycle.
POST to /api/Coda/Crea with party size 2, customer phone number and email, then return the queue code to the host.
Contact and Fidelity Card CRM Lookup
Marketing teams running loyalty programs at Cooperto venues can pull contact records by email or contact code to personalise outreach. The Contatti endpoints return profile details, fidelity status and reservation history, supporting segmentation for SMS and email follow-ups via the venue's existing channels.
GET /api/Contatti/DettagliByEMail with the diner's email and return their fidelity card status and last reservation date.
Reservation Operations Dashboard
Restaurant managers can build a single-pane dashboard that lists today's reservations alongside the live walk-in queue using Cooperto's reservation and Coda endpoints. The bearer-scoped token ensures only the authenticated locale's data is returned, so multi-venue chains can spin up one dashboard per location with isolated credentials.
GET the day's reservation list and live queue for the authenticated locale and merge them into a unified seating timeline.
AI Concierge Agent for Italian Restaurants
An AI host agent can answer questions like 'how long is the wait?' or 'is Marco's table ready?' by calling Cooperto through Jentic. The agent searches by intent, loads the queue lookup schema, and executes against /api/Coda/DettagliByCodice without ever holding the bearer token in its context.
Use Jentic to call /api/Coda/DettagliByCodice with the customer's queue code and return their current position and estimated wait time.
Key Endpoints
38 endpoints — jentic publishes the only available openapi specification for api cooperto.
METHOD
PATH
DESCRIPTION
POST
/api/Coda/Crea
Create a queue entry for a walk-in
POST
/api/Coda/ConfermaArrivo
Confirm customer arrival in the queue
POST
/api/Coda/Elimina
Remove an entry from the queue
GET
/api/Coda/ElencoByCodiceSede
List the live queue for the authenticated venue
GET
/api/Coda/DettagliByCodice
Get queue entry details by queue code
GET
/api/Contatti/DettagliByEMail
Look up a contact by email address
POST
/api/Coda/EseguiAutomazioneManuale
Run a manual automation on a queue entry
POST
/api/Coda/Crea
Create a queue entry for a walk-in
POST
/api/Coda/ConfermaArrivo
Confirm customer arrival in the queue
POST
/api/Coda/Elimina
Remove an entry from the queue
GET
/api/Coda/ElencoByCodiceSede
List the live queue for the authenticated venue
GET
/api/Coda/DettagliByCodice
Get queue entry details by queue code
GET
/api/Contatti/DettagliByEMail
Look up a contact by email address
POST
/api/Coda/EseguiAutomazioneManuale
Run a manual automation on a queue entry
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Cooperto bearer token is stored encrypted in the Jentic credential vault. Agents trigger queue and contact operations through Jentic without the raw token ever entering their reasoning context, and per-venue tokens stay isolated from each other.
Intent-based discovery
Agents search Jentic with intents like 'add walk-in to restaurant queue' or 'look up diner contact by email' and Jentic returns the matching Cooperto operation with its Italian-named parameters mapped to a structured input schema.
Time to first call
Direct integration: 1-2 days to translate the Italian field names, set up bearer auth and handle the queue lifecycle. Through Jentic: under an hour from signup to first queue entry created.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
HubSpot CRM Objects API
Sync Cooperto contact records into a broader CRM for marketing campaigns
Use HubSpot when the venue wants to centralise diner contacts beyond Cooperto's built-in fidelity records.
FAQs
Specific to using API Cooperto.it API through Jentic.
Why is there no official OpenAPI spec for API Cooperto.it?
Cooperto.it does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call API Cooperto.it via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the API Cooperto.it use?
The API uses bearer token authentication scoped to a single venue (locale). Through Jentic the bearer token is held in the credential vault and attached to the Authorization header at execution time.
Can I add a walk-in customer to the queue with the API Cooperto.it?
Yes. POST /api/Coda/Crea accepts the party details (including email or phone) and returns the queue code. You can then call /api/Coda/ConfermaArrivo when the customer shows up and /api/Coda/Elimina when the seat is freed.
What rate limits apply to the API Cooperto.it?
The spec does not document explicit rate limits. Treat operations as transactional, back off on 429 responses, and avoid polling /api/Coda/ElencoByCodiceSede more than once per minute per venue.
How do I look up a contact by email through Jentic with the API Cooperto.it?
Run pip install jentic, search Jentic with 'lookup Cooperto contact by email', load the returned operation schema for /api/Contatti/DettagliByEMail and execute with the diner's email address.
Are the API Cooperto.it field names in Italian?
Yes. Endpoints, parameters and response fields use Italian terms (Coda for queue, Contatti for contacts, ConfermaArrivo for arrival confirmation). Map them in your agent prompts so the agent picks the right operation.
GET STARTED