Docs

OpnForm API Authentication

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

Every OpnForm API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your OpnForm 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

  1. Create a MindCloud account at app.mindcloud.co if you do not already have one.
  2. Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
  3. Create a OpnForm connection in Connections. OpnForm uses an API key. You generate the key in your OpnForm account, then paste it in when you create the connection — MindCloud stores it securely and never returns it in a response.
  4. 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 OpnForm account that should run the action. MindCloud stores and refreshes the OpnForm 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 Workspaces with an OpnForm connection looks like this:

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

Create an OpnForm personal access token

You need an OpnForm account and the abilities required for the actions you want to run.

  1. Open Access Tokens

    Sign in to OpnForm, open Settings > Access Tokens, and click Create new token.

    Settings → Access Tokens
  2. Name the token

    Give the token a clear name such as MindCloud Sandbox.

  3. Select abilities

    Enable workspaces-read, workspaces-write, forms-read, forms-write, workspace-users-read, and workspace-users-write. Also enable manage-integrations if you want webhook integration actions.

  4. Create and copy the token

    Create the token and copy the value immediately. OpnForm will not show it again after you close the dialog.

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.