Mighty Tix API Documentation
This is the complete API documentation for connecting to the Mighty Tix 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 Mighty Tix: Admin GraphQL wrapper for managing accounts, events, sessions, ticket types, venues, users, and orders in Mighty Tix. Keep reading to get started.
Quickstart
Before you run your first Mighty Tix request, you need three things:
- A MindCloud account — sign in or create an account at MindCloud.
- A MindCloud API Key — create one in API Keys. Keep it on your server.
- At least one Mighty Tix connection — create or choose one in Connections. Note its
connectionId.
Every Mighty Tix action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/mightyTix/latest/actions/{actionSlug}You need a MindCloud API Key and a Mighty Tix connection. Then call an action such as Get Account:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/mightyTix/latest/actions/get-account" \
--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 Mighty Tix account that should run the action. MindCloud stores and refreshes the Mighty Tix 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.
Mighty Tix actions
All 41 published actions for this Mighty Tix version. Each page documents the endpoint, arguments, and response controls.
- PUTAdd Session Ticket Types To Session
- POSTCreate Event
- PUTCreate Or Update Session Ticket Types
- POSTCreate Session
- POSTCreate Session Ticket Type
- POSTCreate Ticket Type
- POSTCreate User
- POSTCreate Venue
- DELETEDelete Event
- DELETEDelete Session
- DELETEDelete Session Ticket Type
- DELETEDelete Ticket Type
- DELETEDelete User
- DELETEDelete Venue
- GETGet Account
- GETGet Admin Access Token
- GETGet Event
- GETGet Order
- GETGet Session
- GETGet Session Ticket Type
- GETGet Ticket Type
- GETGet User
- GETGet Venue
- GETList Events
- GETList Orders
- GETList Session Ticket Types
- GETList Sessions
- GETList Ticket Types
- GETList Users
- GETList Venues
- PUTRemove Session Ticket Types From Session
- PUTReorder Ticket Types
- PUTResend Order
- PUTSet Session Ticket Types On Session
- PUTUpdate Account
- PUTUpdate Event
- PUTUpdate Session
- PUTUpdate Session Ticket Type
- PUTUpdate Ticket Type
- PUTUpdate User
- PUTUpdate Venue
Related apps
More Support apps on the Universal API, behind the same REST shape. Or browse all apps.