Billetto API

Name: Billetto API API
Brand: Billetto API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder ManagementapiKey, oauth227 EndpointsREST

For Agents

Pull event attendees and orders, manage audience target groups, fetch BI reports, and subscribe webhooks for a Billetto organiser account.

Quickstart

Get started with Billetto API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list attendees for an event in billetto"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Billetto API API.

Read events, ticket types, and attendee lists for a Billetto organiser account

Fetch orders and ledger entries to reconcile event sales against finance records

Manage audience target groups and add or remove members for segmented marketing

Subscribe webhooks for order, attendee, and event events with rotating secrets

GET STARTED

Start building with Billetto API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Billetto API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Billetto API, keeping it validated and agent-ready. Billetto is a European event ticketing platform and its v3 organiser API exposes the data an organiser team needs to run an event programme: events, ticket types, attendees, orders, campaigns, ledger entries, audience target groups, BI reports, and webhooks. Agents can pull attendee lists for a specific event, reconcile sales via the ledger, segment audiences with target groups, and subscribe webhooks to receive real-time order events.

Use Cases

Patterns agents use Billetto API API for, with concrete tasks.

★ Attendee list export for event ops

Pull the live attendee list for a specific event into a check-in or CRM tool. The API exposes GET /organiser/events/{event_id}/attendees for the event-scoped list and GET /organiser/attendees for an organiser-wide view. Useful for event ops teams running multiple events who need a single export pipeline.

Call GET /organiser/events/{event_id}/attendees for event 12345 and return name, email, and ticket type for each attendee

Sales reconciliation against the ledger

Reconcile event sales against the organiser ledger so finance can close the books on an event series. GET /organiser/orders enumerates ticket orders and GET /organiser/ledger_entries returns the matching financial entries. Pair with GET /organiser/events/{event_id}/bi_report for the consolidated revenue view.

Call GET /organiser/orders for the last 30 days, then GET /organiser/ledger_entries and reconcile order totals against ledger amounts

Audience segmentation

Build segmented audiences for repeat marketing by adding attendees to a target group. POST /organiser/target_group_members adds a member, PATCH /organiser/target_group_members/{id} updates membership, and DELETE removes them. Useful when running re-engagement campaigns to past attendees of a specific event.

Add attendee 67890 to target group ID 42 via POST /organiser/target_group_members, then verify with GET /organiser/target_groups/{id}

Real-time order webhooks

Subscribe a webhook so an agent reacts to new ticket sales, refunds, and attendee changes the moment they happen. POST /organiser/webhooks registers a callback URL, POST /organiser/webhooks/{id}/secret rotates the verification secret, and PATCH adjusts the subscription. Removes the need to poll GET /organiser/orders.

Register a webhook at POST /organiser/webhooks with the agent callback URL, then call POST /organiser/webhooks/{id}/secret to set a verification secret

Agent-driven event ops via Jentic

An AI agent uses Jentic to discover Billetto operations from intents like 'pull attendees for an event' or 'reconcile event sales'. Jentic returns the matching operation, loads its schema, and executes with credentials from the vault. The agent can build an event ops dashboard without ever holding the raw Api-Keypair value.

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

Key Endpoints

27 endpoints — jentic publishes the only available openapi specification for billetto api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/organiser/events

List events

GET

/organiser/events/{event_id}/attendees

List attendees for an event

GET

/organiser/orders

List ticket orders

GET

/organiser/ledger_entries

List ledger entries

GET

/organiser/events/{event_id}/bi_report/

Fetch BI report for an event

POST

/organiser/target_group_members

Add a member to a target group

POST

/organiser/webhooks

POST

/organiser/webhooks/{id}/secret

Rotate a webhook secret

GET

/organiser/events

List events

GET

/organiser/events/{event_id}/attendees

List attendees for an event

GET

/organiser/orders

List ticket orders

GET

/organiser/ledger_entries

List ledger entries

GET

/organiser/events/{event_id}/bi_report/

Fetch BI report for an event

Why though Jentic?

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

Credential isolation

Billetto's Api-Keypair gives broad organiser access and OAuth tokens act on behalf of users. Jentic keeps both encrypted in the vault and only releases a scoped reference at execution time, so a leaked agent context cannot enumerate attendees.

Intent-based discovery

Agents search intents like 'list attendees for an event' or 'subscribe to order webhooks' and Jentic returns the matching organiser operation with its input schema, so the agent does not need to read Billetto's reference docs.

Time to first call

Direct Billetto integration: 1-2 days for OAuth flow, attendee pagination, and webhook secret rotation. Through Jentic: under 30 minutes to the first attendee list pulled.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Ticketmaster Discovery

Ticketmaster Discovery exposes large-venue inventory rather than organiser-side ticketing.

Choose Ticketmaster Discovery when listing or searching events at major venues; choose Billetto for self-organised event programmes that own their attendee data.

Alternative

Ticketmaster Publish

Ticketmaster Publish lets venues list events into Ticketmaster's catalogue.

Choose Publish when targeting Ticketmaster's distribution; choose Billetto when running events on your own ticketing platform.

Complementary

Shopify

Shopify can sell merchandise alongside event tickets handled by Billetto.

Use Shopify alongside Billetto when an event has a merch storefront separate from ticket sales.

FAQs

Specific to using Billetto API API through Jentic.

Why is there no official OpenAPI spec for Billetto API?

Billetto does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Billetto API 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 Billetto API use?

Billetto supports two schemes. The simpler is an API key sent in the Api-Keypair header. For organiser apps that act on behalf of users, OAuth 2.0 authorization-code flow is supported with authorize and token endpoints under billetto.dk/oauth. Through Jentic both keypair and OAuth tokens sit encrypted in the vault.

Can I export attendees for an event with this API?

Yes. Call GET /organiser/events/{event_id}/attendees for the per-event list or GET /organiser/attendees for an organiser-wide view. Each entry returns attendee identity and ticket type, suitable for piping into a check-in tool or CRM.

How do I subscribe to order webhooks through Jentic?

Search Jentic for 'subscribe to billetto order events'. Jentic returns the POST /organiser/webhooks operation, loads its schema, and your agent calls it with the callback URL. Follow with POST /organiser/webhooks/{id}/secret to set a verification secret on the subscription.

What rate limits apply to the Billetto API?

The published spec does not document specific rate limits. In practice Billetto throttles per organiser account, so prefer pagination over GET /organiser/orders or GET /organiser/attendees rather than repeated full-list calls, and back off if HTTP 429 is returned.

Is the Billetto API free?

API access is included with Billetto organiser accounts at no extra cost. You need an active organiser account and either an Api-Keypair or an OAuth client. Jentic does not add usage charges on top.