Evenium API Authentication
How to authenticate Evenium API requests: one Bearer API key plus a connectionId. MindCloud handles Evenium's custom auth scheme for you.
Every Evenium API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Evenium 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 Evenium connection in Connections. Evenium 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 Evenium account that should run the action. MindCloud stores and refreshes the Evenium 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 Evenium connection looks like this:
curl --request POST \
--url "https://connect.mindcloud.co/v2/universal/apps/evenium/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 Evenium account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.
Get your Evenium API token
You need an Evenium organizer account with API access. Evenium API requests must use HTTPS.
- Open your Evenium account API key page
If you use the main Evenium organizer platform, open the API key section in your account and reveal or generate your API key.
My Account → API Key - Use the alternate profile page if your account is on evenium.net
If your organizer account lives on evenium.net instead of evenium.com, use the profile API key page there.
Profile → API Key - Copy the API key
Copy the API key exactly as shown in Evenium.
- Paste the key into the MindCloud connection
When MindCloud asks for the API Key field, paste the Evenium token there. MindCloud will send it in the X-Evenium-Token request header.
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.