Skip to main content

Record Support Release

POST 
/api/support/agent/releases

Records that a build shipped, for the Jira issues named in jira_keys. Every ticket linked (see Add Ticket Link) to one of those issues gets a deploy link, an internal note announcing the release (with your notes appended), and — if it is still unresolved and not already awaiting release — moves to awaiting_release. Any AI drafted reply that was withheld for "awaiting deploy" on those tickets is released, and the agents are alerted that the fix shipped so the next step is to reply and resolve. Nothing customer-facing is sent by this call. Tickets with no matching link are left untouched; duplicate keys are ignored.

Required scope: support:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

Request body:

  • jira_keys[] (required, array, 1-200 items) — issue keys that shipped, each an uppercase project code plus a hyphen and a number (e.g. ENG-4521)
  • build (required, string, max 120) — the build identifier: a commit SHA, tag, or release name
  • url (optional, string, valid absolute URL, max 2048) — a link to the deploy or release notes
  • notes (optional, string, max 5000) — appended to the note posted on each ticket
  • pod (optional, string, max 40) — which environment the release went to

The response lists the ids of the tickets that were touched.

Authentication: Bearer token with the support:write scope, or an authenticated session, from a caller with an active support role that can work tickets.

Request​

Responses​

OK

Response Headers
    Content-Type