Orderry API Documentation

This is the complete API documentation for connecting to the Orderry 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 Orderry: Orderry is a field service and business operations platform for repair shops and service businesses. This app exposes Orderry's public API for contacts, orders, estimates, bookings, inventory, tasks, payments, and settings. Keep reading to get started.

Quickstart

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

Every Orderry action uses the same URL pattern:

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

You need a MindCloud API Key and a Orderry connection. Then call an action such as Get Company Settings:

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

Orderry actions

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

• GETGet Company Settings
• GETGet Company Taxes
• GETGet Organization by ID
• GETGet Person by ID
• GETGet Product by ID
• GETGet Service by ID
• GETList Ad Campaigns
• GETList Asset Custom Fields
• GETList Asset Directories
• GETList Assets
• GETList Bookings
• GETList Cashbox Transactions
• GETList Cashboxes
• GETList Employees
• GETList Estimate Statuses
• GETList Estimates
• GETList Inventory Postings
• GETList Inventory Transfers
• GETList Inventory Write-Offs
• GETList Invoice Statuses
• GETList Invoices
• GETList Lead Custom Fields
• GETList Lead Statuses
• GETList Lead Types
• GETList Leads
• GETList Location Resources
• GETList Locations
• GETList Order Custom Fields
• GETList Order Statuses
• GETList Order Types
• GETList Orders
• GETList Organization People
• GETList Organizations
• GETList People
• GETList Person Organizations
• GETList Prices
• GETList Product Categories
• GETList Products
• GETList Sales
• GETList Service Categories
• GETList Services
• GETList Stock
• GETList Units of Measurement
• GETList Warehouse Bins
• GETList Warehouses

Related apps

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

Google SheetsGmailSlackGoogle CalendarGoogle DriveNotionHubSpotGoogle Forms