RightSignature API Authentication

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

Every RightSignature API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your RightSignature 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 RightSignature connection in Connections. RightSignature uses OAuth. When you create the connection, you are redirected to sign in to RightSignature 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 RightSignature account that should run the action. MindCloud stores and refreshes the RightSignature 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 Get Me with an RightSignature connection looks like this:

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

Connect your RightSignature account

You need ShareFile OAuth credentials for the account and the redirect URI must be registered as https://api.mindcloud.co/v1/oauth/rightSignature/callback.

Confirm the ShareFile OAuth app settings
Use the ShareFile OAuth app credentials that belong to this account and verify the registered redirect URI is exactly https://api.mindcloud.co/v1/oauth/rightSignature/callback.
Start the connection from MindCloud
Click Connect for RightSignature in MindCloud. MindCloud opens the ShareFile authorization flow at secure.sharefile.com.
Sign in and approve access
Sign in to ShareFile and approve the requested access. ShareFile redirects back to MindCloud with the code plus the subdomain and control-plane values needed for token exchange.

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.