Documently API Documentation

This is the complete API documentation for connecting to the Documently 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 Documently: Documently is a documentation management platform for versioning, branching, publishing, file storage, team collaboration, API tokens, and webhooks. Keep reading to get started.

Quickstart

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

Every Documently action uses the same URL pattern:

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

You need a MindCloud API Key and a Documently connection. Then call an action such as List API Tokens:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/documently/latest/actions/list-api-tokens" \
  --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 Documently account that should run the action. MindCloud stores and refreshes the Documently 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.

Documently actions

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

• POSTCreate Branch
• POSTCreate Invitation
• POSTCreate Webhook
• DELETEDelete Branch
• DELETEDelete Webhook
• GETList API Tokens
• GETList Articles
• GETList Branches
• GETList Invitations
• GETList Organizations
• GETList Permissions
• GETList Projects
• GETList Storage Directories
• GETList Storage Files
• GETList Webhook Logs
• GETList Webhooks
• GETRetrieve Branch
• GETRetrieve Current User
• GETRetrieve Invitation
• GETRetrieve Organization
• GETRetrieve Permission
• GETRetrieve Project
• GETRetrieve Storage Directory
• GETRetrieve User
• GETRetrieve Webhook
• PUTUpdate Branch
• PUTUpdate Permission
• PUTUpdate Project
• PUTUpdate Storage Directory
• PUTUpdate User
• PUTUpdate Webhook

Related apps

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

Google CalendarNotionTypeformJira Software CloudSmartsheetCal.comWufooBasecamp