Atlas AI Revenue Engine API Documentation
This is the complete API documentation for connecting to the Atlas AI Revenue Engine 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 Atlas AI Revenue Engine: Manage Atlas campaigns, calls, bookings, and knowledge files. Keep reading to get started.
Quickstart
Before you run your first Atlas AI Revenue Engine 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 Atlas AI Revenue Engine connection — create or choose one in Connections. Note its
connectionId.
Every Atlas AI Revenue Engine action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/atlasAIRevenueEngine/latest/actions/{actionSlug}You need a MindCloud API Key and a Atlas AI Revenue Engine connection. Then call an action such as Get Call Record:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/atlasAIRevenueEngine/latest/actions/get-call-record" \
--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 Atlas AI Revenue Engine account that should run the action. MindCloud stores and refreshes the Atlas AI Revenue Engine 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.
Atlas AI Revenue Engine actions
All 24 published actions for this Atlas AI Revenue Engine version. Each page documents the endpoint, arguments, and response controls.
- POSTAdd Knowledge Base File to Collection
- POSTAttach Knowledge Base File to Campaign
- POSTCreate Scheduled Call
- DELETEDelete Call Record
- DELETEDelete Campaign
- DELETEDelete Knowledge Base File
- DELETEDetach Knowledge Base File from Campaign
- GETGet Call Record
- GETGet Campaign
- GETGet Campaign Statistics
- GETList Call Bookings
- GETList Call Records
- GETList Campaign Bookings
- GETList Campaign Knowledge Base Files
- GETList Campaign Overview Statistics
- GETList Campaigns
- GETList Knowledge Base File Linked Campaigns
- GETList Knowledge Base Files
- GETList Scheduled Calls
- DELETERemove Knowledge Base File from Collection
- PUTSet Campaign Status
- PUTUpdate Campaign
- POSTUpload Knowledge Base File
- POSTUpload Knowledge from URL
Related apps
More Support apps on the Universal API, behind the same REST shape. Or browse all apps.