Bokun API Authentication

How to authenticate Bokun API requests: one Bearer API key plus a connectionId. MindCloud runs the OAuth flow and refreshes Bokun tokens for you.

Every Bokun API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Bokun 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 Bokun connection in Connections. Bokun uses OAuth. When you create the connection, you are redirected to sign in to Bokun and approve access — MindCloud stores the resulting tokens and refreshes them automatically, so your integration never has to.
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 Bokun account that should run the action. MindCloud stores and refreshes the Bokun 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 Time Zones with an Bokun connection looks like this:

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/bokun/actions/list-time-zones/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 Bokun account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect Bokun to MindCloud

You need a Bokun Partner account and a Bokun app that uses OAuth 2.0. Keep your Bokun app API key, API secret, and vendor domain handy before you start the connection.

Create or open your Bokun app in Partner Dashboard
In Bokun Partner Dashboard, go to Apps and create a new app or open the Bokun app you want to connect. Choose Custom app for a single-vendor build unless you need public distribution.
Set the app URL and whitelist the MindCloud callback URL
Add your app URL, then add this exact redirect URL to Bokun's whitelist: https://api.mindcloud.co/v1/oauth/bokun/callback
Copy the Bokun API key and API secret
Bokun's OAuth docs refer to the API key as client_id and the API secret as client_secret. Copy both values from the app overview page.
Install the app for the target vendor
For a custom app, link the app to the target vendor and complete Bokun's install flow so the vendor can grant the requested permissions.
Enter the vendor domain in MindCloud
When MindCloud asks for Vendor Domain, enter the Bokun vendor domain slug only, for example mytours. MindCloud uses that value to build the Bokun authorize and access-token URLs.

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.