Install Jentic One Beta

Connect the Billetto API to your agent

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

Trigger BI reports either inline or by email for an event organiser dashboard

GET STARTED

Start building with Billetto API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Billetto 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 — 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.

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

POST

/organiser/target_group_members

Add a member to a target group

POST

/organiser/webhooks

POST

/organiser/webhooks/{id}/secret

Rotate a webhook secret

Why Jentic?

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

Setup

Wiring the Billetto API by hand means choosing between its key-pair header and an OAuth token acting on behalf of an organiser, then building each event and order path yourself. Through Jentic you install once, import Billetto from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Billetto puts the event id in the URL path (/organiser/events/{event_id}/attendees), so a rule can pin your agent to one event: it can read that event's attendees and reports and nothing else. You choose the operations it may call, so creating target-group members or webhook secrets is not included unless you add them.

Credential isolation

Your Billetto key pair and OAuth tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list attendees for an event' or 'subscribe to order webhooks', and Jentic returns the matching organiser operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Billetto API through Jentic.

Which OpenAPI specification does this Billetto API page describe?

A curated, agent-optimized Jentic specification covering 27 Billetto organiser operations. Billetto also has its own OpenAPI documents: the ReadMe project behind its developer reference at https://api.billetto.com/reference/welcome carries ReadMe-synced OpenAPI files, and the reference is served as browsable pages rather than a spec file at a stable download URL. The Jentic variant is one validated document with agent-facing descriptions and consistent operation naming, kept as a clearly labelled curated spec rather than a substitute for Billetto's own reference. Get started with Jentic One, the self-hosted execution layer.

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.

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

Yes. Jentic One is self-hosted, so your own rules decide which Billetto operations and credentials the agent may use. Because Billetto puts the event id in the URL path, such as GET /organiser/events/{event_id}/attendees, you can pin the agent to a single event so it only reads that event's attendees, orders, and BI report. You also choose exactly which operations it may call, so write actions like POST /organiser/target_group_members or POST /organiser/webhooks/{id}/secret are excluded unless you explicitly allow them.

Billetto Dk Billetto API

Name: Billetto API
Brand: Billetto API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticE CommerceOrder ManagementapiKey, oauth227 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to fetch the attendee list for an event, I want to pull all orders for an upcoming event, Get the ledger entries for the last accounting period, List all events in a Billetto organiser account

Not supported: Does not handle ticket purchase checkout, payment processing, or venue seat-mapping - use for organiser-side event, attendee, order, and audience operations only.

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. Billetto documents this API in its own developer reference, and the specification behind this page is a curated, agent-optimized Jentic document covering 27 of those operations, kept validated and agent-ready so an agent has one consistent file to call.

Jentic One on Github View OpenAPI Document

Connect the Billetto API to your agent

Capabilities

Start building with Billetto API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Billetto Dk Billetto API