GetReplayRecordingSegment response changed from array to typed object
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
The 200 response schema for the "Retrieve a Replay Segment" endpoint has changed from an array of arbitrary objects (array of object with additionalProperties) to a typed object with a required data property containing replayId, segmentId, projectId, and dateAdded fields. This is a breaking change: any client code iterating over the response as an array, or accessing raw segment event data (e.g. type, timestamp, data.tag), will break. The new shape wraps metadata in data and no longer returns the raw recording segment events.