Kadoa API Documentation

This is the complete API documentation for connecting to the Kadoa 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 Kadoa: Extract web data, run workflows, monitor sites, and manage schemas. Keep reading to get started.

Quickstart

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

Every Kadoa action uses the same URL pattern:

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

You need a MindCloud API Key and a Kadoa connection. Then call an action such as Extract Data:

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

Kadoa actions

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

• PUTBulk Approve Rules
• DELETEBulk Delete Rules
• POSTCreate Notification Channel
• POSTCreate Notification Settings
• POSTCreate Schema
• POSTCreate Workflow
• DELETEDelete Notification Channel
• DELETEDelete Notification Settings
• DELETEDelete Schema
• DELETEDelete Workflow
• GETExtract Data
• POSTGenerate Validation Rules
• GETGet Change
• GETGet Crawl Page Content
• GETGet Crawl Pages
• GETGet Crawl Status
• GETGet Event Type
• GETGet Notification Channel
• GETGet Notification Settings
• GETGet Schema
• GETGet Validation Config
• GETGet Validation Results
• GETGet Workflow
• GETGet Workflow Data
• GETGet Workflow History
• GETList Changes
• GETList Event Types
• GETList Locations
• GETList Notification Channels
• GETList Notification Settings
• GETList Schemas
• GETList Validation Rules
• GETList Workflows
• PUTPause Workflow
• PUTResume Workflow
• PUTRun Workflow
• PUTSchedule Workflow
• POSTStart Crawl
• POSTTest Notification
• PUTToggle Validation
• PUTUpdate Notification Channel
• PUTUpdate Notification Settings
• PUTUpdate Schema
• PUTUpdate Workflow Metadata

Related apps

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

JotformFathomStravaCognito FormsPDF.coApifyBrowse AIPdfFiller