Docubee API Documentation

This is the complete API documentation for connecting to the Docubee 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 Docubee: Docubee is a document workflow and eSignature platform for managing documents, workflow templates, workflow instances, signature processes, embedded experiences, and short URL generation. Keep reading to get started.

Quickstart

Before you run your first Docubee 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 Docubee connection — create or choose one in Connections. Note its connectionId.

Every Docubee action uses the same URL pattern:

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

You need a MindCloud API Key and a Docubee connection. Then call an action such as Download Document:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/docubee/latest/actions/download-document" \
  --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 Docubee account that should run the action. MindCloud stores and refreshes the Docubee 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.

Docubee actions

All 28 published actions for this Docubee version. Each page documents the endpoint, arguments, and response controls.

• DELETECancel Instance
• POSTCreate Workflow
• DELETEDelete Document
• DELETEDelete Signature Process
• GETDownload Document
• POSTEmbed Field Placement
• POSTEmbed Signing
• POSTEmbed Web Form
• POSTEmbed Workflow Runtime
• POSTEmbed Workflow Start
• GETExport Workflow
• POSTGenerate Short URL
• GETGet Signature Process Status
• GETGet Workflow Start Form Data
• PUTImport Workflow
• GETList Documents
• GETList Instance Documents
• GETList Instance Properties
• GETList Instance Tasks
• GETList Signature Processes
• GETList Workflow Instances
• GETList Workflows
• POSTReplace Document Content
• PUTSet Document Fields
• POSTStart Signature Process
• POSTStart Workflow
• PUTUpdate Document
• POSTUpload Document

Related apps

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

Google CalendarNotionTypeformJira Software CloudSmartsheetCal.comWufooBasecamp