Update OTLP destination by ID or name
Update an OTLP destination. Sessions already exporting to it pick up the new values without restarting, which makes this the way to rotate credentials without interrupting export.
Names must be unique within the organization. Renaming is refused with a 409 while a managed auth connection selects this destination by name, since that connection resolves the name on every login. Every other field, including headers, stays editable. Requires an organization-scoped credential or dashboard authentication; project-scoped credentials receive a 403.
Authorizations
Body
Fields to update. Omitted fields are left unchanged.
Edits stored headers key by key rather than replacing the map. A string value adds or replaces that header, null deletes it, and any key you omit is left as it is. Names are matched case-insensitively, so authorization replaces a stored Authorization rather than adding a second entry. This is the credential rotation path; sessions already exporting pick up the new values without restarting. Names and values must be valid HTTP header tokens, and the names and values together cannot exceed 8192 bytes.
Response
OTLP destination updated
An OTLP endpoint to export browser session telemetry to. Reference one from telemetry.export.otlp.destination when creating a browser to export that session's captured telemetry to it.
Sanitized class of the delivery failure recorded at last_error_at. It is retained after a later success, so its presence does not mean the destination is currently failing. Response bodies, endpoint URLs, credentials, and raw transport errors are never returned.
512