Cooperto It API Cooperto.it

Name: API Cooperto.it API
Brand: API Cooperto.it
Availability: InStock

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

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.

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

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

GET STARTED

Start building with API Cooperto.it API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Cooperto token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'add a walk-in to the restaurant queue' or 'look up a diner contact by email', and Jentic returns the matching Cooperto operation with its Italian-named parameters mapped to a structured input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Cooperto API?

Yes. Cooperto names each queue and contact action as its own operation, so with your self-hosted Jentic One instance you write the rules that decide which of those operations the agent may call and which credentials it may use. You can allow only the calls it needs, such as creating a queue entry with /api/Coda/Crea and confirming an arrival with /api/Coda/ConfermaArrivo, while leaving deletion via /api/Coda/Elimina and manual automations via /api/Coda/EseguiAutomazioneManuale out of its allowed set. The agent can invoke only the operations you have credited it with, and the bearer token stays with your instance rather than the agent.

Cooperto It API Cooperto.it

Connect the API Cooperto.it to your agent

Capabilities

Start building with API Cooperto.it API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs