PassKit Event Tickets API Authentication
How to authenticate PassKit Event Tickets API requests: one Bearer API key plus a connectionId. MindCloud handles this app's custom auth scheme for you.
Every PassKit Event Tickets API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your PassKit Event Tickets 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 PassKit Event Tickets connection in Connections. PassKit Event Tickets uses its own authentication scheme. You provide whatever it requires when you create the connection — MindCloud handles the provider-specific details for you.
- 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 PassKit Event Tickets account that should run the action. MindCloud stores and refreshes the PassKit Event Tickets 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 Get User Profile with an PassKit Event Tickets connection looks like this:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/passKitEventTickets/latest/actions/get-user-profile" \
--header "Authorization: Bearer $MINDCLOUD_API_KEY" \
--get \
--data-urlencode "connectionId=$CONNECTION_ID"The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which PassKit Event Tickets account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.
Connect PassKit JWT credentials
You need a PassKit account with access to Developer Tools and REST Credentials.
- Open PassKit Developer Tools
Sign in to PassKit and go to the Developer Tools area for your account.
Developer Tools - Open REST Credentials
In Developer Tools, open REST Credentials and create credentials if you do not already have them.
Developer Tools → REST Credentials - Copy the API key and secret into MindCloud
Paste the PassKit API key into the API Key field and the PassKit secret into the API Secret field when creating the connection.
- Save the connection
Save the connection so MindCloud can generate a signed JWT for PassKit API requests.
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.