Install Jentic One Beta

Connect the Billetweb API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Billetweb 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%2Fbilletweb.fr%2Fbilletweb" | 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%2Fbilletweb.fr%2Fbilletweb" | 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 Billetweb API.

List every event in a Billetweb organiser account and read individual event detail

Pull the attendee list for a specific event and look up individual attendees by ID

List orders associated with an event for sales reporting

Read ticket types configured on an event to map pricing and inventory

Look up an individual order by ID for support and reconciliation workflows

GET STARTED

Start building with Billetweb API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Billetweb API for, with concrete tasks.

★ Attendee export for check-in

Pull the attendee list for a specific event into a check-in app or spreadsheet ahead of the door opening. The API exposes GET /events/{eventId}/attendees which returns the per-event roster, and GET /attendees/{attendeeId} for individual lookups when staff need to verify a single ticket. A small events team can power a check-in workflow without exporting CSVs from the Billetweb web UI.

Call GET /events/{eventId}/attendees for event ID 12345 and return name and ticket type for each attendee

Sales reporting across events

Aggregate ticket sales across an organiser's full event programme for a weekly report. The agent calls GET /events to enumerate events, then GET /events/{eventId}/orders for each, summing order totals and attendee counts. Useful for organisers who run a programme of small events and need a single view of revenue.

Call GET /events, then for each call GET /events/{eventId}/orders and return total orders and ticket count per event

CRM enrichment from attendee data

Pipe Billetweb attendee data into a CRM so sales and marketing have context on customers who have attended past events. The agent uses GET /events/{eventId}/attendees to retrieve attendees per event, then matches those records against existing CRM contacts. Ticket-type tagging from GET /events/{eventId}/tickets adds segmentation for downstream campaigns.

Call GET /events/{eventId}/attendees and GET /events/{eventId}/tickets, then build a tag list of attendees by ticket type for the CRM

Order lookup for support

Resolve a buyer's question about a specific order without leaving the support tool. The agent calls GET /orders/{orderId} with the order ID provided by the customer to return the matching event, attendee, and ticket-type detail. Pair with GET /attendees/{attendeeId} when the question is about a specific ticket holder.

Call GET /orders/{orderId} for order ID 99887 and return the matching event ID, attendee count, and total amount

Agent-driven event reporting via Jentic

An AI agent uses Jentic to discover Billetweb operations from intents like 'list attendees for an event' or 'get sales for an event'. Jentic returns the matching GET operation, loads its schema, and executes with the bearer token from the vault. The agent can build a multi-event report without ever holding the raw token directly.

Search Jentic for 'list attendees for an event in billetweb', load the schema, and execute it for event ID 12345

Key Endpoints

7 endpoints — this page describes a curated, agent-optimized jentic specification for billetweb api, covering seven read-only operations and kept validated and agent-ready; billetweb also publishes its own wider openapi document, which adds write operations this reporting slice does not carry.

METHOD

PATH

DESCRIPTION

GET

/events

List events

GET

/events/{eventId}

Get an individual event

GET

/events/{eventId}/attendees

List attendees for an event

GET

/events/{eventId}/orders

List orders for an event

GET

/events/{eventId}/tickets

List ticket types for an event

GET

/attendees/{attendeeId}

Get an individual attendee

GET

/orders/{orderId}

Get an individual order

GET

/events

List events

GET

/events/{eventId}

Get an individual event

GET

/events/{eventId}/attendees

List attendees for an event

GET

/events/{eventId}/orders

List orders for an event

GET

/events/{eventId}/tickets

List ticket types for an event

GET

/attendees/{attendeeId}

Get an individual attendee

GET

/orders/{orderId}

Get an individual order

Why Jentic?

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

Setup

Wiring the Billetweb API by hand means carrying its bearer token on every call and building each read-only event, attendee, and order path yourself. Through Jentic you install once, import Billetweb from the API Directory, store the token once, and your agent calls it.

Permission scoping

Billetweb puts the event id in the URL path (/events/{eventId}/attendees, /events/{eventId}/orders), so a rule can pin your agent to one event and its attendees and orders. Every operation here is read-only reporting, so no write path is reachable regardless of the set you allow.

Credential isolation

Your Billetweb bearer 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 'list attendees for an event' or 'get sales for an event', and Jentic returns the matching Billetweb operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Billetweb API through Jentic.

Which OpenAPI specification does this Billetweb API page describe?

A curated, agent-optimized Jentic specification covering seven read-only Billetweb operations for events, attendees, orders, and ticket types. Billetweb also publishes its own OpenAPI document at `https://www.billetweb.fr/api/openapi.json`, a wider 37-operation surface that adds campaigns, CRM contacts and segments, lists, forms, payouts, and accounting, plus write operations for orders and events. The Jentic variant stays on the narrow read-only reporting slice, validated against the live API and kept agent-ready, so no purchase, payment, or write path is reachable through it. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Billetweb API use?

Billetweb uses HTTP bearer-token authentication. Pass the token in the Authorization: Bearer header on every request. Through Jentic the bearer token sits encrypted in the vault and the agent only ever holds a scoped reference.

Can I export attendees from this API?

Yes. Call GET /events/{eventId}/attendees to retrieve every attendee on a specific event, and GET /attendees/{attendeeId} for an individual lookup. The endpoints return enough identity and ticket-type detail to populate a check-in tool or CRM contact.

How do I pull event sales through Jentic?

Search Jentic for 'list orders for a billetweb event'. Jentic returns the GET /events/{eventId}/orders operation, loads its schema, and your agent calls it with the event ID. Pair with GET /events to enumerate events first when reporting across the full programme.

What rate limits apply to the Billetweb API?

The published spec does not document specific rate limits. The endpoint surface is read-only and small (7 endpoints), so polling at modest intervals is generally safe; for high-volume reporting use GET /events/{eventId}/orders with pagination rather than per-attendee fan-out.

Is the Billetweb API free?

API access is included with Billetweb organiser accounts at no extra cost. You need an active organiser account and a bearer token issued from the Billetweb dashboard. Jentic does not add usage charges on top.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Billetweb operations and credentials your agent may use. Since the event id sits in the URL path on calls like GET /events/{eventId}/attendees and GET /events/{eventId}/orders, you can pin the agent to a single event and its attendees and orders rather than the whole account. Every Billetweb operation here is read-only, so no purchase, payment, or write path is reachable no matter which endpoints you allow.

Billetweb Fr Billetweb API

Name: Billetweb API
Brand: Billetweb API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticE CommerceOrder Managementbearer7 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Pull event, attendee, order, and ticket-type data from a Billetweb organiser account for reporting, CRM sync, and check-in workflows.

Use for: I need to fetch the attendee list for an event on Billetweb, I want to list every event in our Billetweb organiser account, Get the orders for a specific event, Retrieve the ticket types configured on an event

Not supported: Does not handle ticket purchase, payment processing, or webhook subscriptions - use for read-only event, attendee, and order reporting only.

This page describes a curated, agent-optimized Jentic specification for Billetweb API, covering seven read-only operations and kept validated and agent-ready; Billetweb also publishes its own wider OpenAPI document, which adds write operations this reporting slice does not carry. Billetweb is a French event ticketing platform and this API is a read-oriented surface that lets organisers pull events, ticket types, attendees, and orders into external dashboards. Agents can list every event in the account, drill into a specific event for its attendees and orders, and look up an individual attendee or order by ID. The seven-endpoint surface keeps the integration narrow and predictable for reporting and CRM sync.

Jentic One on Github View OpenAPI Document