SupportBee API Documentation

This is the complete API documentation for connecting to the SupportBee 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 SupportBee: SupportBee is a customer support help desk and shared inbox platform for managing tickets, replies, comments, teams, labels, and inbox workflows. Keep reading to get started.

Quickstart

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

Every SupportBee action uses the same URL pattern:

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

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

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

SupportBee actions

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

• PUTAdd Label to Ticket
• PUTArchive Ticket
• PUTAssign Ticket to Team
• PUTAssign Ticket to User
• POSTCreate Comment
• POSTCreate Reply
• POSTCreate Ticket
• GETGet Ticket
• GETGet User
• GETList Labels
• GETList Teams
• GETList Ticket Comments
• GETList Ticket Replies
• GETList Tickets
• GETList Users
• PUTMark Ticket Answered
• PUTMark Ticket as Spam
• PUTMark Ticket Unanswered
• PUTRestore Ticket
• GETSearch Tickets
• PUTTrash Ticket
• PUTUnarchive Ticket
• PUTUnassign Ticket from Team
• PUTUnassign Ticket from User

Related apps

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

TrelloClickUpZendeskQuoIntercomEventbriteTickTickLinear