Skip to main content
PATCH
The Update Log endpoint allows you to modify specific fields of a single log. This is useful for adding annotations, updating metadata, or correcting information.
For updating multiple logs at once, use the Batch Update endpoint.

Updatable fields

The following fields can be updated:
  • metadata - Custom metadata properties
  • custom_identifier - Custom identifier
  • blurred - Privacy flag to blur log content

Core log data is immutable

Fields like input, output, log_type, model, usage, cost, latency, and other telemetry fields cannot be modified to maintain data integrity.

Path parameters

string
required
The unique ID of the log to update. You can get this from the List Logs endpoint.

Body parameters

object
Update the log’s metadata with custom properties. This can be used for tagging, categorization, or adding context.
string
Update the log’s custom identifier. Useful for linking logs to external systems.
boolean
Set whether the log content should be blurred for privacy reasons.

Response

Returns the complete updated log object (same structure as the Get Log endpoint).

Use Cases

Metadata Best Practices

Organizing metadata

  1. Use consistent keys: Establish naming conventions across your organization
  2. Add timestamps: Include _at or _timestamp fields for tracking when metadata was added
  3. Namespace related fields: Use prefixes like review_, feedback_, experiment_ to group related fields
  4. Keep it queryable: Use simple data types (strings, numbers, booleans) for fields you’ll filter on
  5. Document your schema: Maintain documentation of your metadata structure

Error Responses