eSign Genie API Authentication

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

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

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

Connect Foxit eSign

You need Foxit eSign API access for your Foxit eSign account. Foxit documents that eSign API credentials come from the separate Foxit eSign Portal, not the general Foxit Developer Portal.

Sign in to the Foxit eSign Portal
Open the Foxit eSign Portal and sign in with the account that should own the eSign API access.
Foxit eSign Portal
Confirm eSign API access is enabled
If you do not see eSign API credentials or API settings for your account, contact Foxit to enable eSign API access for your tenant. Foxit documents that eSign API access is separately provisioned.
Copy the Client ID and Client Secret
From the Foxit eSign Portal/API settings, copy the Client ID and Client Secret for the eSign API integration.
Enter the credentials in MindCloud
Paste the Foxit eSign Client ID and Client Secret into the MindCloud connection form. MindCloud will request an OAuth2 access token with the documented read-write scope.

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.