PostHog API Authentication

How to authenticate PostHog API requests: one Bearer API key plus a connectionId. MindCloud stores your PostHog API key securely — set it once, never resend it.

Every PostHog API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your PostHog 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 PostHog connection in Connections. PostHog uses an API key. You generate the key in your PostHog 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 PostHog account that should run the action. MindCloud stores and refreshes the PostHog 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 Organizations with an PostHog connection looks like this:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/postHog/latest/actions/list-organizations" \
  --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 PostHog account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Set up your PostHog personal API key

Sign in to the same PostHog instance that MindCloud will access, such as your US cloud, EU cloud, or self-hosted PostHog workspace.

Open Personal API keys in your PostHog account settings
Go to the Personal API keys section in your PostHog account settings for the workspace where you want MindCloud to run.
Create a new personal API key
Click + Create a personal API Key, give it a label that describes its MindCloud use, and choose only the scopes required for the endpoints you want MindCloud to call.
Copy the new key immediately
Copy the personal API key value as soon as it appears. PostHog does not show the full key again after you leave or refresh the page.
Paste the key into MindCloud
Enter the copied value into the MindCloud PostHog connection as the API Key credential.

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.