Billetto API Documentation

This is the complete API documentation for connecting to the Billetto API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet Billetto: Billetto is an event ticketing platform for organizers, audiences, public event discovery, reporting, webhooks, and target group management. Keep reading to get started.

Quickstart

Before you run your first Billetto request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one Billetto connection — create or choose one in Connections. Note its connectionId.

Every Billetto action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/billetto/latest/actions/{actionSlug}

You need a MindCloud API Key and a Billetto connection. Then call an action such as List Attendees:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/billetto/latest/actions/list-attendees" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Billetto account that should run the action. MindCloud stores and refreshes the Billetto credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

Billetto actions

All 36 published actions for this Billetto version. Each page documents the endpoint, arguments, and response controls.

• POSTCreate Target Group Import
• POSTCreate Target Group Member
• POSTCreate Webhook
• DELETEDelete Target Group
• DELETEDelete Target Group Member
• DELETEDelete Webhook
• POSTEmail BI Report
• POSTGenerate Webhook Secret
• GETList Attendees
• GETList Campaigns
• GETList Event Attendees
• GETList Event Campaigns
• GETList Events
• GETList Import Members
• GETList Ledger Entries
• GETList Orders
• GETList Public Events
• GETList Target Group Imports
• GETList Target Group Imports By Target Group
• GETList Target Group Members
• GETList Target Groups
• GETList Ticket Types
• GETList Webhooks
• GETRetrieve Attendee
• GETRetrieve BI Report
• GETRetrieve Campaign
• GETRetrieve Event
• GETRetrieve Event Campaign
• GETRetrieve Ledger Entry
• GETRetrieve Order
• GETRetrieve Public Event
• GETRetrieve Target Group
• GETRetrieve Webhook
• DELETERevoke Webhook Secret
• PUTUpdate Target Group Member
• PUTUpdate Webhook

Related apps

More apps on the Universal API, behind the same REST shape. Or browse all apps.

Google SheetsGmailSlackGoogle CalendarGoogle DriveNotionHubSpotGoogle Forms