SupportBee
BUSINESS · CRM & SUPPORT
Tickets, replies, labels, and teams on the desk that person belongs to.
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_idWRITEDelete snippet via DELETE /snippets/{id}
supportbee_delete_tickets_by_idWRITEDelete a trashed ticket via DELETE /tickets/{id}
supportbee_delete_tickets_by_id_answeredWRITEMark a ticket as un-answered via DELETE /tickets/{id}/answered
supportbee_delete_tickets_by_id_archiveWRITEUn-archive a ticket via DELETE /tickets/{id}/archive
supportbee_delete_tickets_by_id_draftWRITEDelete draft via DELETE /tickets/{id}/draft
supportbee_delete_tickets_by_id_spamWRITEUn-spam a ticket via DELETE /tickets/{id}/spam
supportbee_delete_tickets_by_id_team_assignmentWRITEUn-assign a ticket from its team via DELETE /tickets/{id}/team_assignment
supportbee_delete_tickets_by_id_trashWRITEUn-trash a ticket via DELETE /tickets/{id}/trash
supportbee_delete_tickets_by_id_user_assignmentWRITEUn-assign a ticket from its user via DELETE /tickets/{id}/user_assignment
supportbee_delete_tickets_by_ticket_id_labels_by_label_nameWRITERemove label via DELETE /tickets/{ticket_id}/labels/{label_name}
supportbee_get_emailsREADFetch emails via GET /emails
supportbee_get_labelsREADFetch labels via GET /labels
supportbee_get_reports_avg_first_response_timeREADAverage first response time report via GET /reports/avg_first_response_time
supportbee_get_reports_replies_countREADReplies count report via GET /reports/replies_count
supportbee_get_reports_tickets_countREADTickets count report via GET /reports/tickets_count
supportbee_get_snippetsREADFetch snippets via GET /snippets
supportbee_get_teamsREADFetch teams via GET /teams
supportbee_get_ticketsREADList tickets via GET /tickets
supportbee_get_tickets_by_idREADRetrieve a ticket via GET /tickets/{id}
supportbee_get_tickets_by_id_auditREADFetch audit trail via GET /tickets/{id}/audit
supportbee_get_tickets_by_id_commentsREADFetch comments via GET /tickets/{id}/comments
supportbee_get_tickets_by_id_draftREADFetch draft via GET /tickets/{id}/draft
supportbee_get_tickets_by_id_repliesREADFetch ticket replies via GET /tickets/{id}/replies
supportbee_get_tickets_by_ticket_id_replies_by_idREADShow a reply via GET /tickets/{ticket_id}/replies/{id}
supportbee_get_tickets_searchREADSearch tickets via GET /tickets/search
supportbee_get_usersREADFetch users and customer groups via GET /users
supportbee_get_users_by_idREADShow user or customer group via GET /users/{id}
supportbee_get_users_by_id_membersREADFetch members of a customer group via GET /users/{id}/members
supportbee_post_consequencesWRITECreate consequence via POST /consequences
supportbee_post_emailsWRITECreate email via POST /emails
supportbee_post_filtersWRITECreate filter via POST /filters
supportbee_post_rulesWRITECreate rule via POST /rules
supportbee_post_snippetsWRITECreate snippet via POST /snippets
supportbee_post_ticketsWRITECreate ticket via POST /tickets
supportbee_post_tickets_by_id_answeredWRITEMark a ticket as answered via POST /tickets/{id}/answered
supportbee_post_tickets_by_id_archiveWRITEArchive a ticket via POST /tickets/{id}/archive
supportbee_post_tickets_by_id_commentsWRITECreate comment via POST /tickets/{id}/comments
supportbee_post_tickets_by_id_draftWRITECreate draft via POST /tickets/{id}/draft
supportbee_post_tickets_by_id_repliesWRITECreate a reply via POST /tickets/{id}/replies
supportbee_post_tickets_by_id_spamWRITEMark ticket as spam via POST /tickets/{id}/spam
supportbee_post_tickets_by_id_team_assignmentWRITEAssign a ticket to a team via POST /tickets/{id}/team_assignment
supportbee_post_tickets_by_id_trashWRITETrash ticket via POST /tickets/{id}/trash
supportbee_post_tickets_by_id_user_assignmentWRITEAssign a ticket to a user via POST /tickets/{id}/user_assignment
supportbee_post_tickets_by_ticket_id_labels_by_label_nameWRITEAdd label via POST /tickets/{ticket_id}/labels/{label_name}
supportbee_post_usersWRITECreate a user or customer group via POST /users
supportbee_post_users_by_id_membersWRITEAdd member via POST /users/{id}/members
supportbee_put_snippets_by_idWRITEUpdate snippet via PUT /snippets/{id}
supportbee_put_tickets_by_id_draftWRITEUpdate draft via PUT /tickets/{id}/draft
supportbee_put_users_by_idWRITEUpdate a user via PUT /users/{id}
Often connected alongside
Put SupportBee behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.