Docs

eSign Genie API Documentation

This is the complete API documentation for connecting to the eSign Genie API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet eSign Genie: Manage Foxit eSign envelopes, templates, webhooks, reports, and user administration from the Foxit eSign API. Keep reading to get started.

Quickstart

Before you run your first eSign Genie request, you need three things:

  1. A MindCloud account — sign in or create an account at MindCloud.
  2. A MindCloud API Key — create one in API Keys. Keep it on your server.
  3. At least one eSign Genie connection — create or choose one in Connections. Note its connectionId.

Every eSign Genie action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/eSignGenie/latest/actions/{actionSlug}

You need a MindCloud API Key and a eSign Genie connection. Then call an action such as Download Envelope Files:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/eSignGenie/latest/actions/download-envelope-files" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

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. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

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.

  1. 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
  2. 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.

  3. 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.

  4. 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.

eSign Genie actions

All 30 published actions for this eSign Genie version. Each page documents the endpoint, arguments, and response controls.

More Productivity apps on the Universal API, behind the same REST shape. Or browse all apps.