QuintaDB API Documentation

This is the complete API documentation for connecting to the QuintaDB 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 QuintaDB: Build forms, manage databases, and automate business workflows. Keep reading to get started.

Quickstart

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

Every QuintaDB action uses the same URL pattern:

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

You need a MindCloud API Key and a QuintaDB connection. Then call an action such as Get Database:

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

QuintaDB actions

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

• POSTCreate Database
• POSTCreate Field
• POSTCreate Form
• POSTCreate Record
• DELETEDelete All Records
• DELETEDelete Database
• DELETEDelete Field
• DELETEDelete Form
• DELETEDelete Many Records
• DELETEDelete Record
• GETGet Database
• GETGet Database By Name
• GETGet Field
• GETGet Field Total
• GETGet Form
• GETGet Form By Name
• GETGet Record
• GETGet Relation Field ID
• GETList Databases
• GETList Fields
• GETList Forms
• GETList Records
• GETList Reports
• PUTRemove File
• GETRun Field Action
• GETRun Field Actions
• GETSearch Records
• PUTUpdate All Records
• PUTUpdate Cell Value
• PUTUpdate Database
• PUTUpdate Field
• PUTUpdate Form
• PUTUpdate Many Records
• PUTUpdate Record

Related apps

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

GitHubNetlifyMySQLPostgreSQLFirebasePagerDutyGoogle Workspace AdminAdalo