Skip to main content
TroopyDocs
Open Troopy
Troopy

API reference / Support Agent

Get where the bug tickets of chats go

The GitHub repo and the branch of the bug tickets that the Support agent makes of chats. Null: the Engineer picks the repo, and the work starts from its default branch.

get/api/v1/support-ticket-settings

Authorization

HeaderAuthorization: Bearer <API key>
Or the headerX-API-Key: <API key>
API keyMake one in Troopy under Settings > API keys. It acts as you, in its workspace.

Other ways to call it

CLItroopy support ticket-settings
MCP tooltroopy_get_support_ticket_settings
Rate limit60 calls in 60 seconds, for each key
RetriesSend an Idempotency-Key header. A retry with the same key gets the first answer back, and the operation runs one time.

Response

200 · application/json
data*object
2 properties
repo*string | null

The GitHub repo that each bug ticket of a chat changes, as owner/name. Null: the Engineer picks the repo

branch*string | null

The branch that the work of each bug ticket of a chat starts from, and that its pull request goes into, like staging. Null: the default branch of the repo. A ticket keeps the branch that was set when Troopy made it

Errors

401 unauthorizedSend an API key as `Authorization: Bearer tr_live_...`. Create one in Troopy under Settings.
403 forbiddenThe key lacks a scope this operation needs, or its owner lacks the role. detail says which; create a key with the scope, or ask an organization owner or admin.
409 conflictThis Idempotency-Key was used for a different request, or that request is still running. Use a new key for a new request.
429 rate_limitedWait the number of seconds in Retry-After, then retry.