Ticket Tailor API Authentication

How to authenticate Ticket Tailor API requests: one Bearer API key plus a connectionId. MindCloud stores your credentials — no auth headers to build.

Every Ticket Tailor API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Ticket Tailor account. This page covers both, plus exactly how to send them, so you do not need to visit any other page to get authenticated.

Steps to authenticate

Create a MindCloud account at app.mindcloud.co if you do not already have one.
Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
Create a Ticket Tailor connection in Connections. Ticket Tailor uses a username and password. You enter them when you create the connection — MindCloud stores them securely so your requests never carry raw credentials.
Copy the connection’s connectionId — you will send it on every request alongside your MindCloud API Key.

How requests are authenticated

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 Ticket Tailor account that should run the action. MindCloud stores and refreshes the Ticket Tailor 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.

For example, calling List Events with an Ticket Tailor connection looks like this:

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/ticketTailor/actions/list-events/run" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "arguments": {}
}'

The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which Ticket Tailor account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect Ticket Tailor with HTTP Basic auth

You need a Ticket Tailor account with access to the box office you want to connect.

Open the API settings in Ticket Tailor
Sign in to Ticket Tailor, open your box office settings, and select API.
Box office settings → API
Create or copy a secret API key
Generate or copy the secret API key for the box office you want MindCloud to access. Ticket Tailor notes that API keys are box-office specific.
Enter the credentials in MindCloud
In the MindCloud connection form for Ticket Tailor, paste the Ticket Tailor secret API key into the Username field.
Leave Password blank
Ticket Tailor's docs state that HTTP Basic auth should use your API key as the username and a blank password.

Keep your key safe

Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs. Anyone with the key can call the Universal API as your MindCloud account, across every connection you have created.