Get daily latency percentiles for an agent

curl --request GET \
  --url "http://localhost:8002/api/v1/agent/latency-percentiles/?start_date=2026-03-24&end_date=2026-03-26" \
  --header "X-OTAS-USER-TOKEN: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." \
  --header "X-OTAS-AGENT-ID: a1b2c3d4-e5f6-7890-abcd-ef1234567890" \
  --header "X-OTAS-PROJECT-ID: 3f6e2b10-8c1a-4d55-b9d4-0a2e3c7f1234"

{
  "status": 1,
  "agent_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "project_id": "3f6e2b10-8c1a-4d55-b9d4-0a2e3c7f1234",
  "data": [
    {
      "date": "2026-03-24",
      "p50": 98.2,
      "p95": 312.5,
      "p99": 890.0
    },
    {
      "date": "2026-03-25",
      "p50": 142.3,
      "p95": 489.1,
      "p99": 1203.7
    },
    {
      "date": "2026-03-26",
      "p50": 105.8,
      "p95": 298.4,
      "p99": 744.2
    }
  ]
}

{
  "status": 0,
  "status_description": "start_date must be before or equal to end_date"
}

{
  "status": 0,
  "status_description": "agent_not_found"
}

curl --request GET \
  --url "http://localhost:8002/api/v1/agent/latency-percentiles/?start_date=2026-03-24&end_date=2026-03-26" \
  --header "X-OTAS-USER-TOKEN: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." \
  --header "X-OTAS-AGENT-ID: a1b2c3d4-e5f6-7890-abcd-ef1234567890" \
  --header "X-OTAS-PROJECT-ID: 3f6e2b10-8c1a-4d55-b9d4-0a2e3c7f1234"

{
  "status": 1,
  "agent_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "project_id": "3f6e2b10-8c1a-4d55-b9d4-0a2e3c7f1234",
  "data": [
    {
      "date": "2026-03-24",
      "p50": 98.2,
      "p95": 312.5,
      "p99": 890.0
    },
    {
      "date": "2026-03-25",
      "p50": 142.3,
      "p95": 489.1,
      "p99": 1203.7
    },
    {
      "date": "2026-03-26",
      "p50": 105.8,
      "p95": 298.4,
      "p99": 744.2
    }
  ]
}

{
  "status": 0,
  "status_description": "start_date must be before or equal to end_date"
}

{
  "status": 0,
  "status_description": "agent_not_found"
}

This endpoint returns daily latency percentile data for an agent — p50 is the median response time, p95 captures the experience of the large majority of requests, and p99 reveals worst-case behaviour. All values are in milliseconds. Use this data to render latency distribution charts and detect performance regressions over time before they affect most users.

Request

string

required

JWT identifying the authenticated user.

string

required

UUID of the agent to retrieve latency data for.

string

required

UUID of the project the agent belongs to.

Query parameters

string

required

Start of the date range, inclusive. Must be in YYYY-MM-DD format.

string

required

End of the date range, inclusive. Must be in YYYY-MM-DD format and must not be before start_date.

Response

number

required

1 on success.

string

required

The agent UUID from the request headers.

string

required

The project UUID from the request headers.

object[]

required

Daily latency percentile entries, ordered by date ascending.

Show data point properties

string

required

Date in YYYY-MM-DD format.

number

required

50th percentile (median) latency in milliseconds, rounded to 1 decimal place. null if no events exist for this date.

number

required

95th percentile latency in milliseconds, rounded to 1 decimal place.

number

required

99th percentile latency in milliseconds, rounded to 1 decimal place.

Percentiles are computed using PostgreSQL’s PERCENTILE_CONT function, which performs exact linear interpolation between adjacent values. Only dates that have at least one event are included — there is no zero-fill for days without traffic.

If p99 is significantly higher than p95 on a given day, there are likely a small number of outlier requests driving the tail. Use the session events endpoint to identify those specific calls by filtering for sessions on that date and sorting by latency_ms.

Errors

HTTP	`status_description`	Meaning
400	`missing_dates`	`start_date` or `end_date` query parameter was not provided.
400	`invalid_date_format`	One or both dates are not in `YYYY-MM-DD` format.
400	`invalid_date_range`	`start_date` is after `end_date`.
401	`missing_user_token`	`X-OTAS-USER-TOKEN` header was not provided.
400	`missing_agent_id`	`X-OTAS-AGENT-ID` header was not provided.
400	`missing_project_id`	`X-OTAS-PROJECT-ID` header was not provided.
403	`forbidden`	The authenticated user does not have access to the specified project.
404	`agent_not_found`	No active agent matches the provided agent ID.
503	`auth_service_timeout`	The UASAM auth service did not respond within the timeout window.
503	`auth_service_error`	The UASAM auth service is unreachable.
500	`server_error`	An unexpected internal error occurred.

curl --request GET \
  --url "http://localhost:8002/api/v1/agent/latency-percentiles/?start_date=2026-03-24&end_date=2026-03-26" \
  --header "X-OTAS-USER-TOKEN: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." \
  --header "X-OTAS-AGENT-ID: a1b2c3d4-e5f6-7890-abcd-ef1234567890" \
  --header "X-OTAS-PROJECT-ID: 3f6e2b10-8c1a-4d55-b9d4-0a2e3c7f1234"

{
  "status": 1,
  "agent_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "project_id": "3f6e2b10-8c1a-4d55-b9d4-0a2e3c7f1234",
  "data": [
    {
      "date": "2026-03-24",
      "p50": 98.2,
      "p95": 312.5,
      "p99": 890.0
    },
    {
      "date": "2026-03-25",
      "p50": 142.3,
      "p95": 489.1,
      "p99": 1203.7
    },
    {
      "date": "2026-03-26",
      "p50": 105.8,
      "p95": 298.4,
      "p99": 744.2
    }
  ]
}

{
  "status": 0,
  "status_description": "start_date must be before or equal to end_date"
}

{
  "status": 0,
  "status_description": "agent_not_found"
}

UASAM — Users & Auth

UASAM — Projects & Keys

UASAM — Agents

Brain — Event Capture

Brain — Analytics

Get daily latency percentiles for an agent

Request

Query parameters

Response

Errors

​Request

​Query parameters

​Response

​Errors

Request

Query parameters

Response

Errors