DataCrush API Documentation

This is the complete API documentation for connecting to the DataCrush 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 DataCrush: DataCrush is a CRM and marketing automation platform with REST API endpoints for contacts, accounts, opportunities, and ecommerce entities. Keep reading to get started.

Quickstart

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

Every DataCrush action uses the same URL pattern:

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

You need a MindCloud API Key and a DataCrush connection. Then call an action such as Search Accounts:

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

DataCrush actions

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

• PUTAdd Contact To Account
• PUTAdd Contact To Opportunity
• PUTChange Opportunity Stage
• POSTCreate Account
• POSTCreate Contact
• POSTCreate Ecommerce Category
• POSTCreate Ecommerce Customer
• POSTCreate Ecommerce Order
• POSTCreate Ecommerce Product
• POSTCreate Opportunity
• DELETEDelete Account
• DELETEDelete Contact
• DELETEDelete Opportunity
• PUTRemove Contact From Account
• PUTRemove Contact From Opportunity
• GETSearch Accounts
• GETSearch Accounts By Domain
• GETSearch Contacts
• GETSearch Contacts By Contact Key
• GETSearch Contacts By Email
• GETSearch Contacts By Lifecycle
• GETSearch Contacts In List
• GETSearch Opportunities
• PUTUpdate Account
• PUTUpdate Contact
• PUTUpdate Ecommerce Category
• PUTUpdate Ecommerce Customer
• PUTUpdate Ecommerce Order
• PUTUpdate Ecommerce Product
• PUTUpdate Opportunity

Related apps

More Sales & CRM apps on the Universal API, behind the same REST shape. Or browse all apps.

HubSpotPipedriveGoogle TasksGoogle ContactsTodoistZoho CRMFollow Up BossClose