Qntrl API Documentation
This is the complete API documentation for connecting to the Qntrl 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 Qntrl: Qntrl: Manage cards, forms, blueprints, and workflow activity. Keep reading to get started.
Quickstart
Before you run your first Qntrl 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 Qntrl connection — create or choose one in Connections. Note its
connectionId.
Every Qntrl action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/qntrl/latest/actions/{actionSlug}You need a MindCloud API Key and a Qntrl connection. Then call an action such as Export Users:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/qntrl/latest/actions/export-users" \
--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 Qntrl account that should run the action. MindCloud stores and refreshes the Qntrl 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.
Qntrl actions
All 42 published actions for this Qntrl version. Each page documents the endpoint, arguments, and response controls.
- GETExport Users
- GETGet Attachment Details
- GETGet Blueprint Details
- GETGet Card Comment Details
- GETGet Card Details
- GETGet Custom Field Details
- GETGet Custom View Details
- GETGet Form Details
- GETGet My User Details
- GETGet Organization Details
- GETGet Profile Details
- GETGet Report Details
- GETGet Report Folder Details
- GETGet Role Details
- GETGet Row Details
- GETGet Stage Details
- GETGet Table Details
- GETGet Transition Rule
- GETGet User Activity
- GETGet User Details
- GETList Active Blueprints
- GETList Blueprints
- GETList Card Activities
- GETList Card Attachments
- GETList Card Comments
- GETList Cards
- GETList Custom Fields
- GETList Custom Views
- GETList Deleted Cards
- GETList Forms
- GETList Next Card Transitions
- GETList Organizations
- GETList Profile Permissions
- GETList Profiles
- GETList Report Folders
- GETList Reports
- GETList Roles
- GETList Rows
- GETList Stages
- GETList Tables
- GETList User Dropdown Values
- GETList Users
Related apps
More apps on the Universal API, behind the same REST shape. Or browse all apps.