canonical: https://jentic.com/apis/lebillet.eu/lebillet

# LeBillet - API de Assentos

The LeBillet API lists, reserves, and activates event seating. A caller can see which seats are available for a specific event, hold a chosen seat by its id, and then activate that reservation with the buyer's payment totals and contact details. Requests are authenticated with HTTP basic auth.

## For AI agents

List available seats for an event, reserve a seat by id, and activate the reservation with the buyer's payment and contact details.

## Scope

Does not handle event creation, catalog browsing, or refunds. Use for listing, reserving, and activating event seats only.

## Capabilities

- List the seats still available for a specific event
- Reserve a chosen seat by its id for an event
- Activate a reserved seat with the buyer's payment totals and contact details

## Use cases

### Book an event seat with an AI agent

An AI agent integration created through Jentic walks a buyer through choosing a seat. The LeBillet API lists the available seats for an event, reserves the one the buyer picks by its id, and activates it once payment totals and contact details are known, so the agent completes a seat booking end to end.

Example prompt: List available seats for an event, reserve the chosen seat by id, then activate it with the buyer's totals

### Show live seat availability

A storefront needs to show which seats are still open for an event. The LeBillet API returns the available seats for an event id, so an automation can render a live availability map and avoid offering seats that are already taken.

Example prompt: Retrieve the available seats for an event id and present them as a list

### Confirm a reservation after payment

Once a buyer pays, the held seat must be confirmed with the transaction details. The LeBillet API activates a reserved seat using its code and the payment totals including tax, discount, and the total value, along with the buyer's email, so an agent finalizes the sale against the correct seat.

Example prompt: Activate a reserved seat with its code, payment totals, and the buyer's email

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api_seats/seats/{id_event}` | List available seats for an event |
| POST | `/api_seats/reserveSeat` | Reserve a seat |
| POST | `/api_seats/activeSeat` | Activate a reserved seat |

## Key resources

- **Seats** — List the seats available for an event
- **Reservations** — Reserve a seat by id and activate it with payment and contact details

## 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:** 30 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 79 / 100
  - AI-Readiness & Agent Experience: 18 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/lebillet.eu/lebillet/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 LeBillet by hand means setting up HTTP basic auth and tracking seat and event ids across the reservation and activation calls. Through Jentic you install once, import LeBillet from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** LeBillet puts the event id in the URL path for listing seats, so a rule can limit your agent to reading availability for one event. Reservation and activation carry the ids in the request body, so rules bound which operations your agent may call, such as listing and reserving while leaving activation out unless you add it.
- **Credential handling:** Your LeBillet credential 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 'reserve a seat' or 'list available seats', and Jentic returns the matching LeBillet operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Eventbrite** — Eventbrite manages event creation, ticketing, and attendees; LeBillet is scoped to listing, reserving, and activating seats.
- **SeatGeek** — SeatGeek exposes event and ticket listings across venues; LeBillet handles direct seat reservation for your own events.
- **Mollie** — Mollie processes European payments; pair it with LeBillet to collect payment before activating a reserved seat.

## FAQ

### What authentication does the LeBillet API use?

The LeBillet API authenticates with HTTP basic auth, per its OpenAPI spec. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.

### Can I reserve a seat with the LeBillet API?

Yes. The reserve operation holds a seat by its id for an event, and the activate operation confirms that reservation with the buyer's payment totals and contact details, so an agent can take a seat from available to confirmed.

### What details are needed to activate a seat?

Activation requires the seat and event ids, a code, the payment values for product, tax, discount, and total, and the buyer's email and cell number, all sent in the request body. Supplying these finalizes the reservation against the correct seat.

### How do I book an event seat through Jentic?

Install Jentic One on your own infrastructure with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the LeBillet API from the API Directory and search for 'reserve an event seat'. Store the credential once and your agent can list, reserve, and activate seats. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a LeBillet MCP server?

You don't need an MCP server to give your agent the LeBillet API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, with each operation discovered on demand instead of loaded into the agent's context.

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

Yes. The seat listing operation puts the event id in the URL path, so a rule can let the agent read availability and reserve seats while leaving activation out, so it cannot finalize a sale on its own. Every action it takes is recorded in an audit log.