PassKit Membership API Authentication
How to authenticate PassKit Membership API requests: one Bearer API key plus a connectionId. MindCloud stores your PassKit Membership API key securely — set…
Every PassKit Membership API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your PassKit Membership 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 Membership connection in Connections. PassKit Membership uses an API key. You generate the key in your PassKit Membership account, then paste it in when you create the connection — MindCloud stores it securely and never returns it in a response.
- 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 Membership account that should run the action. MindCloud stores and refreshes the PassKit Membership 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 Programs with an PassKit Membership connection looks like this:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/passKitMembership/latest/actions/list-programs" \
--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 Membership account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.
Connect your PassKit Membership account with a long-lived token
You need a PassKit long-lived API token and the correct API Prefix for your region.
- Open the Membership program settings
In PassKit, open the membership program you want MindCloud to use, then open Settings and go to Pass APIs.
Program → Settings → Pass APIs - Generate the long-lived API token
Enter your account password and click Generate API Token, then copy the token shown in the popup. This token grants permanent API access to that PassKit program.
- Copy the correct API Prefix
Use https://api.pub2.passkit.io for US accounts and https://api.pub1.passkit.io for EU accounts, based on the API region shown in your PassKit developer tools.
- Enter the values in MindCloud
Paste the long-lived token into the main API Key field and enter the API Prefix in the extra field for this connection.
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.