Dovkie
Sign in
Back to Sentry API
Sentry API

Trace response: timestamps changed to double, event_type narrowed to enums

BreakingBreaking change

This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.

What changed

Several breaking changes to trace response schemas:

  • start_timestamp and end_timestamp changed from string (date-time) to number (double) — clients parsing ISO timestamps will break.
  • event_type changed from an open string to a closed enum ("span", "error", "occurrence", "uptime_check" depending on context) — clients that write/validate against the old free-form string type may reject valid values or fail validation.
  • event_type removed from the required array in children items, making it no longer guaranteed to be present there.
  • measurements, browser_web_vital, and mobile_app_vital additionalProperties narrowed from {} (any type) to number (double).

Open the source documentation