fynk API Documentation
This is the complete API documentation for connecting to the fynk 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 fynk: Create and manage fynk documents, templates, metadata, signatories, parties, file storage, comments, and document stage transitions. Keep reading to get started.
Quickstart
Before you run your first fynk request, you need three things:
- A MindCloud account — sign in or create an account at MindCloud.
- A MindCloud API Key — create one in API Keys. Keep it on your server.
- At least one fynk connection — create or choose one in Connections. Note its
connectionId.
Every fynk action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/fynk/latest/actions/{actionSlug}You need a MindCloud API Key and a fynk connection. Then call an action such as Download Latest Revision PDF:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/fynk/latest/actions/download-latest-revision-pdf" \
--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 fynk account that should run the action. MindCloud stores and refreshes the fynk 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.
fynk actions
All 39 published actions for this fynk version. Each page documents the endpoint, arguments, and response controls.
- POSTCreate Document File Storage Upload URL
- POSTCreate Document From PDF
- POSTCreate Document From Template
- POSTCreate Document Metadata Value
- POSTCreate Document Party
- POSTCreate Document PDF Upload URL
- POSTCreate Document Signatory
- POSTCreate Document Stored File
- DELETEDelete Document Metadata Value
- DELETEDelete Document Signatory
- GETDownload Latest Revision PDF
- GETGet Current API Token Details
- GETGet Document
- GETGet Document Comment
- GETGet Document Stored File
- GETGet Latest Revision PDF Details
- GETGet Template
- POSTLink Documents
- GETList Document Comments
- GETList Document Dynamic Fields
- GETList Document Metadata Values
- GETList Document Parties
- GETList Document Signatories
- GETList Document Stored Files
- GETList Documents
- GETList Linked Documents
- GETList Metadata
- GETList Tags
- GETList Templates
- PUTMove Document To Done Stage
- PUTMove Document To Review Stage
- PUTMove Document To Signing Stage
- PUTSet Signing Order
- DELETEUnlink Documents
- PUTUpdate Document
- PUTUpdate Document Dynamic Field
- PUTUpdate Document Metadata Value
- PUTUpdate Document Party
- PUTUpdate Document Signatory
Related apps
More Productivity apps on the Universal API, behind the same REST shape. Or browse all apps.