Skip to content
AppHandoff AppHandoff Docs

Update safe fields on a linked ticket

PATCH
/integrations/context-capture/v1/tickets/{ticketId}
 
curl --request PATCH \
  --url https://example.com/api/integrations/context-capture/v1/tickets/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "expectedRevision": "2026-04-15T12:00:00Z", "title": "example", "description": "example", "priority": "low", "status": "open" }'

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
ticketId
required
string format: uuid

Request Body required

Section titled “Request Body required ”
Media type application/json
object
expectedRevision
required
string format: date-time
title
string
>= 5 characters <= 140 characters
description
string
>= 10 characters <= 5000 characters
priority
string
Allowed values: low medium high
status
string
Allowed values: open closed

Responses

Section titled “ Responses ”

200

Section titled “200 ”

Updated ticket

Media type application/json
object
id
required
string format: uuid
number
required
integer
>= 1
title
required
string
status
required
string
Allowed values: open closed
stage
required
string
Allowed values: backlog up_next in_progress validation live
priority
required
string
Allowed values: low medium high
revision
required
string format: date-time
updatedAt
required
string format: date-time
portalUrl
required
string format: uri
resolutionType
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”.

string | null
survivingTicketRef

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.

string | null

401

Section titled “401 ”

Not authenticated

Media type application/json
object
error
required

Human-readable error message

string
code

Stable machine-readable error code for client branching

string
fieldErrors

First validation message per field path

object
key
additional properties
string
issues

Structured validation issues (Zod)

Array<object>
object
path
required
string
message
required
string
retryAfter

Seconds until rate limit resets (429 responses)

number
reconnect

True if re-linking GitHub may fix the issue

boolean

404

Section titled “404 ”

Not found

Media type application/json
object
error
required

Human-readable error message

string
code

Stable machine-readable error code for client branching

string
fieldErrors

First validation message per field path

object
key
additional properties
string
issues

Structured validation issues (Zod)

Array<object>
object
path
required
string
message
required
string
retryAfter

Seconds until rate limit resets (429 responses)

number

409

Section titled “409 ”

Revision conflict

422

Section titled “422 ”

Invalid request

Media type application/json
object
error
required

Human-readable error message

string
code

Stable machine-readable error code for client branching

string
fieldErrors

First validation message per field path

object
key
additional properties
string
issues

Structured validation issues (Zod)

Array<object>
object
path
required
string
message
required
string
retryAfter

Seconds until rate limit resets (429 responses)

number

429

Section titled “429 ”

Rate limited