RightSignature API Documentation

This is the complete API documentation for connecting to the RightSignature 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 RightSignature: Send, sign, and manage documents, reusable templates, and signature workflows with RightSignature. Keep reading to get started.

Quickstart

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

Every RightSignature action uses the same URL pattern:

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

You need a MindCloud API Key and a RightSignature connection. Then call an action such as Get Archived Document By Original GUID:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/rightSignature/latest/actions/get-archived-document-by-original-guid" \
  --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 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. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

RightSignature actions

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

• PUTAdd Or Update Reusable Template Tags
• POSTCreate Sending Request
• DELETEDelete Reusable Template
• DELETEDelete Reusable Template Tag
• POSTEmbed Document From Reusable Template
• GETGet Archived Document By Original GUID
• GETGet Document
• GETGet Me
• GETGet Reusable Template
• GETGet Sending Request
• GETList Documents
• GETList Reusable Template Tags
• GETList Reusable Templates
• POSTMark Sending Request Uploaded
• POSTMerge And Send Document
• POSTPrepare Document From Reusable Template
• POSTReplace Reusable Template Tags
• POSTRequest OAuth Access Token
• GETRequest OAuth Authorization Code
• POSTRevoke OAuth Access Token
• POSTSend Document From Reusable Template
• POSTSend Signer Reminder
• POSTShare Document
• PUTUpdate Document PIN
• POSTUpdate Document Tags
• POSTVoid Document

Related apps

More Content & Files apps on the Universal API, behind the same REST shape. Or browse all apps.

Google DriveAirtableGoogle DocsDropboxGoogle SlidesWorkflowyZoho SheetSnowflake