Sales Cookie API Documentation

This is the complete API documentation for connecting to the Sales Cookie 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 Sales Cookie: Import transactions and read commission calculations and incentive data. Keep reading to get started.

Quickstart

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

Every Sales Cookie action uses the same URL pattern:

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

You need a MindCloud API Key and a Sales Cookie connection. Then call an action such as Get Custom Properties:

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

Sales Cookie actions

All 33 published actions for this Sales Cookie version. Each page documents the endpoint, arguments, and response controls.

• POSTAdd User To Team
• PUTCreate Or Update Team
• PUTCreate Or Update User
• POSTCreate Transaction
• GETGet Custom Properties
• POSTImport Transactions
• GETList Alerts
• GETList Announcements
• GETList Calculation Commissions
• GETList Calculation Credits
• GETList Calculation Results
• GETList Calculations
• GETList Catalog Entries
• GETList Custom Variables
• GETList Event Logs
• GETList Plan Enrollments
• GETList Plan Roles
• GETList Plans
• GETList Reports
• GETList Survey Results
• GETList Surveys
• GETList Team Aliases
• GETList Team Members
• GETList Teams
• GETList Transactions
• GETList User Aliases
• GETList Users
• GETList Workspace Roles
• GETList Workspace Settings
• POSTPrepare Full Transaction Import
• DELETERemove User From Team
• PUTSet Custom Properties
• POSTUpload Transactions Csv

Related apps

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

Google SheetsGmailSlackGoogle CalendarGoogle DriveNotionHubSpotGoogle Forms