Update an output

Corrects the bookkeeping on an output already in Tracira: the metadata attached to it, the shared IDs that file it under a conversation or a customer, and the label on each stored file.

Use it when context arrives after the output did: a CRM ticket number, a category your classifier decided later, the role a file turned out to play.
The record itself is immutable. Input, output, verdict and human decision cannot be edited here - they are what the manager judged.
Metadata merges by default: only the keys you send change, and a key sent empty is removed.
Editing metadata returns 409 while the output is still being evaluated, because the evaluation rewrites that column when it lands. Labels and context IDs can be set at any time.
Changing metadata does not re-run the rules: a verdict belongs to the output that was judged.

patchhttps://www.tracira.com/api/logs/{id}

Authorization

AuthorizationBearer <token>

Workspace webhook token from Settings -> Integrations.

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Every field is optional, but the request must change something. Input, output, verdict and decision are never editable: they are the record that was judged.

metadata?

Key-value pairs to store on the output. In the default merge mode only the keys you send change; a key sent with an empty value (null or a blank string) is removed, matching how ingest drops empty values. 0 and false are values and are kept. Sending metadata: null in merge mode changes nothing, so an unmapped integration field never wipes what is stored.

metadataMode?string

merge (default) applies the keys you send on top of what is stored. replace stores exactly what you send and drops everything else - metadata: {} with replace clears all metadata. Requires metadata to be present.

Default"merge"

Value in

"merge"
"replace"

attachments?array<>

Files on this output to relabel.

Itemsitems <= 40

sessionId?string

Backfill the session/conversation ID. All the ingest aliases work here too (conversationId, threadId, chatId, snake_case included), top-level or inside metadata.

subjectId?string

Backfill the subject ID - the customer, ticket, account or record the output is about. Aliases: customerId, recordId, ticketId, accountId.

actorId?string

Backfill the actor ID - who triggered the execution. Aliases: endUserId, userId, agentId.

Response Body

`application/json`

curl -X PATCH "https://example.com/api/logs/b7d1c9e4-3f2a-4d5b-9c81-0a6e7f2b4d13" \  -H "Content-Type: application/json" \  -d '{    "metadata": {      "ticket_id": "1042",      "crm_stage": "escalated"    }  }'

{  "ok": true,  "id": "string",  "metadata": {},  "sessionId": "string",  "subjectId": "string",  "actorId": "string",  "attachments": [    {      "role": "input",      "type": "image",      "filename": "invoice-april.pdf",      "contentType": "application/pdf",      "key": "1f4a8c60-92d7-4b3e-8a51-c27e6d90f3b2/log-42/0-ab12cd34-invoice-april.pdf",      "url": "https://www.tracira.com/api/media/1f4a8c60-92d7-4b3e-8a51-c27e6d90f3b2/log-42/0-ab12cd34-invoice-april.pdf",      "label": "Before photo"    }  ]}

Update an output

Authorization

Path Parameters

Request Body

Response Body

200application/json

400application/json

401application/json

404application/json

409application/json

429application/json

`application/json`

`application/json`

`application/json`

`application/json`

`application/json`

`application/json`