All integrations

SupportBee

BUSINESS · CRM & SUPPORT

Tickets, replies, labels, and teams on the desk that person belongs to.

Connecting SupportBee in practice

SupportBee’s Create Ticket endpoint is the only one that works without authentication, and unauthenticated it is capped at 5 requests per hour per IP address to keep spammers out. Authenticated, the same endpoint allows 8 tickets per minute, which is the tightest documented ceiling in the API.

Scopes that draw scrutiny

  • Authorization: Bearer your_api_token One account-wide token with no scopes. The documentation also shows it as an `auth_token=` query parameter for attachment uploads, which puts the credential into URLs and therefore into logs.

Rate limits

  • Create Ticket without authentication: 5 API requests per hour per IP address.
  • Create Ticket with authentication: 8 tickets per minute.
  • Over either limit the endpoint responds with 429.
  • List Tickets pagination: `per_page` defaults to 15 and "must be less than 100".

Worth knowing

  • The Accept header must be set to application/json, so a client relying on content negotiation defaults can get the wrong representation.
  • All date and time parameters must be supplied in UTC — there is no timezone parameter to lean on.
  • Tickets come back sorted by last activity unless you pass `sort_by`, so a pagination pass over a busy inbox can see the same ticket twice as it moves.
  • The unauthenticated Create Ticket path is genuinely open, so anything that embeds it client-side is publishing a ticket-creation endpoint.

Checked against SupportBee API reference (2026-09-29)

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

supportbee_delete_snippets_by_idWRITE

Delete snippet via DELETE /snippets/{id}

api
supportbee_delete_tickets_by_idWRITE

Delete a trashed ticket via DELETE /tickets/{id}

api
supportbee_delete_tickets_by_id_answeredWRITE

Mark a ticket as un-answered via DELETE /tickets/{id}/answered

api
supportbee_delete_tickets_by_id_archiveWRITE

Un-archive a ticket via DELETE /tickets/{id}/archive

api
supportbee_delete_tickets_by_id_draftWRITE

Delete draft via DELETE /tickets/{id}/draft

api
supportbee_delete_tickets_by_id_spamWRITE

Un-spam a ticket via DELETE /tickets/{id}/spam

api
supportbee_delete_tickets_by_id_team_assignmentWRITE

Un-assign a ticket from its team via DELETE /tickets/{id}/team_assignment

api
supportbee_delete_tickets_by_id_trashWRITE

Un-trash a ticket via DELETE /tickets/{id}/trash

api
supportbee_delete_tickets_by_id_user_assignmentWRITE

Un-assign a ticket from its user via DELETE /tickets/{id}/user_assignment

api
supportbee_delete_tickets_by_ticket_id_labels_by_label_nameWRITE

Remove label via DELETE /tickets/{ticket_id}/labels/{label_name}

api
supportbee_get_emailsREAD

Fetch emails via GET /emails

api
supportbee_get_labelsREAD

Fetch labels via GET /labels

api
supportbee_get_reports_avg_first_response_timeREAD

Average first response time report via GET /reports/avg_first_response_time

api
supportbee_get_reports_replies_countREAD

Replies count report via GET /reports/replies_count

api
supportbee_get_reports_tickets_countREAD

Tickets count report via GET /reports/tickets_count

api
supportbee_get_snippetsREAD

Fetch snippets via GET /snippets

api
supportbee_get_teamsREAD

Fetch teams via GET /teams

api
supportbee_get_ticketsREAD

List tickets via GET /tickets

api
supportbee_get_tickets_by_idREAD

Retrieve a ticket via GET /tickets/{id}

api
supportbee_get_tickets_by_id_auditREAD

Fetch audit trail via GET /tickets/{id}/audit

api
supportbee_get_tickets_by_id_commentsREAD

Fetch comments via GET /tickets/{id}/comments

api
supportbee_get_tickets_by_id_draftREAD

Fetch draft via GET /tickets/{id}/draft

api
supportbee_get_tickets_by_id_repliesREAD

Fetch ticket replies via GET /tickets/{id}/replies

api
supportbee_get_tickets_by_ticket_id_replies_by_idREAD

Show a reply via GET /tickets/{ticket_id}/replies/{id}

api
supportbee_get_tickets_searchREAD

Search tickets via GET /tickets/search

api
supportbee_get_usersREAD

Fetch users and customer groups via GET /users

api
supportbee_get_users_by_idREAD

Show user or customer group via GET /users/{id}

api
supportbee_get_users_by_id_membersREAD

Fetch members of a customer group via GET /users/{id}/members

api
supportbee_post_consequencesWRITE

Create consequence via POST /consequences

api
supportbee_post_emailsWRITE

Create email via POST /emails

api
supportbee_post_filtersWRITE

Create filter via POST /filters

api
supportbee_post_rulesWRITE

Create rule via POST /rules

api
supportbee_post_snippetsWRITE

Create snippet via POST /snippets

api
supportbee_post_ticketsWRITE

Create ticket via POST /tickets

api
supportbee_post_tickets_by_id_answeredWRITE

Mark a ticket as answered via POST /tickets/{id}/answered

api
supportbee_post_tickets_by_id_archiveWRITE

Archive a ticket via POST /tickets/{id}/archive

api
supportbee_post_tickets_by_id_commentsWRITE

Create comment via POST /tickets/{id}/comments

api
supportbee_post_tickets_by_id_draftWRITE

Create draft via POST /tickets/{id}/draft

api
supportbee_post_tickets_by_id_repliesWRITE

Create a reply via POST /tickets/{id}/replies

api
supportbee_post_tickets_by_id_spamWRITE

Mark ticket as spam via POST /tickets/{id}/spam

api
supportbee_post_tickets_by_id_team_assignmentWRITE

Assign a ticket to a team via POST /tickets/{id}/team_assignment

api
supportbee_post_tickets_by_id_trashWRITE

Trash ticket via POST /tickets/{id}/trash

api
supportbee_post_tickets_by_id_user_assignmentWRITE

Assign a ticket to a user via POST /tickets/{id}/user_assignment

api
supportbee_post_tickets_by_ticket_id_labels_by_label_nameWRITE

Add label via POST /tickets/{ticket_id}/labels/{label_name}

api
supportbee_post_usersWRITE

Create a user or customer group via POST /users

api
supportbee_post_users_by_id_membersWRITE

Add member via POST /users/{id}/members

api
supportbee_put_snippets_by_idWRITE

Update snippet via PUT /snippets/{id}

api
supportbee_put_tickets_by_id_draftWRITE

Update draft via PUT /tickets/{id}/draft

api
supportbee_put_users_by_idWRITE

Update a user via PUT /users/{id}

api

Put SupportBee behind one governed endpoint.

Same permissions, same audit trail, whatever else you connect next.