Ascora API Documentation

This is the complete API documentation for connecting to the Ascora 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 Ascora: Ascora: Manage leads, quotes, jobs, inventory, invoicing, and reporting. Keep reading to get started.

Quickstart

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

Every Ascora action uses the same URL pattern:

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

You need a MindCloud API Key and a Ascora connection. Then call an action such as Get Customer:

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

Ascora actions

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

• PUTAdd Kits To Quote
• PUTAdd Labour To Quote
• PUTAdd Quote Sections
• PUTAdd Supplies To Quote
• PUTAdd Write-Ins To Quote
• PUTClear Quote Items
• POSTCreate Customer
• POSTCreate Enquiry
• POSTCreate Full Section-Based Quote
• POSTCreate Job
• POSTCreate Payment
• POSTCreate Quote
• POSTCreate Quote With Items
• POSTCreate Supplier
• POSTCreate Supplier Invoice
• POSTCreate Webhook Subscription
• DELETEDelete Quote Or Section
• GETGet Customer
• GETGet Invoices To Send
• GETGet Job
• GETGet Payments To Send
• GETGet Quote
• GETGet Supplier Invoice
• GETList Categories
• GETList Contacts
• GETList Contacts For Customer
• GETList Customers
• GETList Jobs
• GETList Kits
• GETList Labour Roles
• GETList Quotes
• GETList Supplier Invoices
• GETList Suppliers
• GETList Supplies
• PUTMark Invoices Sent
• PUTMark Payments Sent
• PUTUpdate Customer
• PUTUpdate Quote Status
• PUTUpdate Supplier
• POSTUpsert Contact

Related apps

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

TrelloClickUpZendeskQuoIntercomEventbriteTickTickLinear