Get a project's key timing milestones as absolute, comparable timestamps

Returns the project's timing milestones on a single server clock, so a consumer can measure how long QA took to start producing activity and to finish without draining event streams.

Fields:

  • created_at — when the project was created (ISO 8601 UTC).
  • started_at — when work actually began (earliest task start), or null if none has started yet.
  • first_event_at — server-side arrival time of the earliest rrweb event across ALL of the project's recordings (explorations + test runs); null if no events yet.
  • finished_at — when the project last went idle; null while QA is still running.
  • time_to_first_event_ms / time_to_complete_ms — deltas measured from created_at (null when the corresponding timestamp is null).
get/api/v1/projects/{project_id}/timing

Request

  • Base URL: https://qa.replay.io
  • URL: https://qa.replay.io/api/v1/projects/{project_id}/timing
  • Auth: HTTP bearer

Path parameters

project_idstring required

Response

Project timing milestones

Changes

No recorded changes to this operation across all 1 revision of this API.