Billetweb API Documentation

This is the complete API documentation for connecting to the Billetweb 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 Billetweb: Manage events, ticket sales, attendees, and payouts. Keep reading to get started.

Quickstart

Before you run your first Billetweb 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 Billetweb connection — create or choose one in Connections. Note its connectionId.

Every Billetweb action uses the same URL pattern:

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

You need a MindCloud API Key and a Billetweb connection. Then call an action such as Get Campaign Content:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/billetweb/latest/actions/get-campaign-content" \
  --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 Billetweb account that should run the action. MindCloud stores and refreshes the Billetweb 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.

Billetweb actions

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

• POSTAdd List Entry
• POSTAdd Offline Order
• POSTCreate Event From Template
• PUTCreate Or Update Event Sessions
• PUTCreate Or Update Event Tickets
• GETGet Campaign Content
• GETGet List Content
• GETList Accounting Entries
• GETList All Attendees
• GETList Campaigns
• GETList CRM Contacts
• GETList CRM Segments
• GETList Event Attendees
• GETList Event Availability
• GETList Event Sessions
• GETList Event Tickets
• GETList Event Waiting List
• GETList Events
• GETList Lists
• GETList Payouts
• GETList Session Changes
• GETList Shared Forms
• PUTReplace List Contents

Related apps

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

TrelloClickUpZendeskQuoIntercomEventbriteTickTickLinear