Order Sender API Documentation

This is the complete API documentation for connecting to the Order Sender 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 Order Sender: Order Sender Business API wrapper for exporting, importing, and deleting business data such as orders, products, customers, suppliers, discounts, quotes, and price lists. Keep reading to get started.

Quickstart

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

Every Order Sender action uses the same URL pattern:

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

You need a MindCloud API Key and a Order Sender connection. Then call an action such as List Commissions:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/orderSender/latest/actions/list-commissions" \
  --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 Order Sender account that should run the action. MindCloud stores and refreshes the Order Sender 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.

Order Sender actions

All 28 published actions for this Order Sender version. Each page documents the endpoint, arguments, and response controls.

• DELETEDelete Customers
• DELETEDelete Discounts
• DELETEDelete Payment Conditions
• DELETEDelete Products
• DELETEDelete Prospects
• DELETEDelete Secondary Addresses
• POSTImport Commissions
• POSTImport Customer Payment Conditions
• POSTImport Customers
• POSTImport Discounts
• POSTImport Payment Conditions
• POSTImport Price Lists
• POSTImport Products
• POSTImport Prospects
• POSTImport Secondary Addresses
• POSTImport Suppliers
• GETList Commissions
• GETList Customer Payment Conditions
• GETList Customers
• GETList Discounts
• GETList Orders
• GETList Payment Conditions
• GETList Price Lists
• GETList Products
• GETList Prospects
• GETList Quotes
• GETList Suppliers
• GETVerify Connection

Related apps

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

Google SheetsGmailSlackGoogle CalendarGoogle DriveNotionHubSpotGoogle Forms