ContextCapture

Create or replay a ticket for one Context Capture report

Private integration endpoint. A project-bound ah_cc credential files into its own project and ignores projectId. An account-scoped credential requires projectId, which must belong to the credential's billing account.

post/integrations/context-capture/v1/tickets

Request

Base URL: https://api.apphandoff.com/api
URL: https://api.apphandoff.com/api/integrations/context-capture/v1/tickets
Auth: HTTP bearer

Request body

externalReportIdstring required

titlestring required

descriptionstring required

projectIdstring uuid

Target project. Required for an account-scoped credential and ignored by a project-bound one.

priority'low' | 'medium' | 'high'

Reporter-chosen severity. Filed at medium when absent.

Example request

{
  "attachments": [
    {
      "contentType": "image/png"
    }
  ]
}

Response

Existing linked ticket

idstring uuid required

numberinteger required

titlestring required

status'open' | 'closed' required

stage'backlog' | 'up_next' | 'in_progress' | 'validation' | 'live' required

priority'low' | 'medium' | 'high' required

revisionstring date-time required

updatedAtstring date-time required

portalUrlstring uri required

resolutionTypestring nullable required

How the ticket was actually resolved, so a customer-facing status can say "merged into HO-n" or "closed, not built" instead of "Resolved". Every closed ticket lands in stage live regardless of outcome, so stage alone cannot tell a shipped fix from a duplicate/cancelled/wont_fix close. Null on an open ticket, and null on a closed ticket that carries neither a stored resolution nor a merge — absence means "closed, nothing proven", never "completed".

survivingTicketRefstring nullable

For a duplicate close, the ticket that survived (e.g. HO-11216). Best-effort: no stored duplicate link type exists yet, so this is parsed from the free-prose resolution note and is absent when the note names no ticket. Absent on every non-duplicate resolution.

Changes

No recorded changes to this operation across all 1 revision of this API.