Write to an incident's timeline
Changed onAppend a row to an incident's timeline, returning the event it wrote.
eventType says what the row records - COMMENT_ADDED (the default) for an ordinary comment, or AI_DIAGNOSIS_REQUESTED, AI_DIAGNOSIS_COMPLETED and AI_DIAGNOSIS_FAILED to record the start, result or failure of a diagnosis.
agentSessionId names the Orchestra agent session behind the write. The row is then attributed to Orchestra AI and linked to that session rather than to the API key; an agent takes the id from its ORCHESTRA_AGENT_SESSION_ID environment variable. The AI_DIAGNOSIS_* types require it. A session may write several over its life, but posting the same text twice returns the row already written.
description sets the incident's description alongside an AI_DIAGNOSIS_COMPLETED or AI_DIAGNOSIS_FAILED row, and needs edit permission on the incident. It is not applied over a description a person wrote.
The timeline is append-only: nothing can edit or delete a row once it is there.
Request
- Base URLhttps://app.getorchestra.io/api/engine/public
- URLhttps://app.getorchestra.io/api/engine/public/incidents/{incident_id}/comments
- Auth
- HTTP bearer
- or OAuth 2Authorization code: https://app.getorchestra.io/oauth/authorizeToken URL: https://app.getorchestra.io/oauth/token scopes: orchestra:write
Path parameters
Incident ID.
Headers
Act on this account rather than the one the credential resolves to. Omit it to use the credential's own account. An API key is issued to a single account, so it may only name that account; an OAuth token may name any account its grant covers.
Request body
Response
Successful Response
Changes
- info
endpoint added
- info