CentralStationCRM API Documentation
This is the complete API documentation for connecting to the CentralStationCRM 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 CentralStationCRM: Manage contacts, deals, tasks, and team sales work. Keep reading to get started.
Quickstart
Before you run your first CentralStationCRM 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 CentralStationCRM connection — create or choose one in Connections. Note its
connectionId.
Every CentralStationCRM action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/centralStationCRM/latest/actions/{actionSlug}You need a MindCloud API Key and a CentralStationCRM connection. Then call an action such as Check Connection:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/centralStationCRM/latest/actions/check-connection" \
--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 CentralStationCRM account that should run the action. MindCloud stores and refreshes the CentralStationCRM 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.
CentralStationCRM actions
All 40 published actions for this CentralStationCRM version. Each page documents the endpoint, arguments, and response controls.
- GETCheck Connection
- GETCount Companies
- GETCount Deals
- GETCount People
- POSTCreate Company
- POSTCreate Deal
- POSTCreate Person
- POSTCreate Project
- POSTCreate Protocol
- POSTCreate Task
- DELETEDelete Company
- DELETEDelete Person
- DELETEDelete Task
- GETGet Company
- GETGet Current User
- GETGet Deal
- GETGet Person
- GETGet Project
- GETGet Protocol
- GETGet Task
- GETGet User
- GETList Companies
- GETList Deals
- GETList People
- GETList Projects
- GETList Protocols
- GETList Tasks
- GETList Users
- PUTMerge Companies
- PUTMerge People
- GETSearch Companies
- GETSearch Deals
- GETSearch People
- GETSearch Records
- GETSearch Users
- PUTUpdate Company
- PUTUpdate Deal
- PUTUpdate Person
- PUTUpdate Project
- PUTUpdate Task
Related apps
More Sales & CRM apps on the Universal API, behind the same REST shape. Or browse all apps.