Get per-path event counts over time

curl --request GET \
  --url "http://localhost:8002/api/v1/agent/path-timeseries/?start_date=2026-03-01&end_date=2026-03-07" \
  --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",
  "paths": [
    {
      "path": "/api/v1/orders/",
      "data": [
        { "date": "2026-03-01", "count": 14 },
        { "date": "2026-03-02", "count": 9 },
        { "date": "2026-03-04", "count": 22 }
      ]
    },
    {
      "path": "/api/v1/users/",
      "data": [
        { "date": "2026-03-01", "count": 10 },
        { "date": "2026-03-02", "count": 7 }
      ]
    }
  ]
}

{
  "status": 0,
  "status_description": "start_date and end_date are required"
}

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

curl --request GET \
  --url "http://localhost:8002/api/v1/agent/path-timeseries/?start_date=2026-03-01&end_date=2026-03-07" \
  --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",
  "paths": [
    {
      "path": "/api/v1/orders/",
      "data": [
        { "date": "2026-03-01", "count": 14 },
        { "date": "2026-03-02", "count": 9 },
        { "date": "2026-03-04", "count": 22 }
      ]
    },
    {
      "path": "/api/v1/users/",
      "data": [
        { "date": "2026-03-01", "count": 10 },
        { "date": "2026-03-02", "count": 7 }
      ]
    }
  ]
}

{
  "status": 0,
  "status_description": "start_date and end_date are required"
}

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

The path-timeseries endpoint returns a breakdown of how many events each API path received per day over the requested date range. Each path in the response carries its own array of { date, count } entries, making it straightforward to render a multi-line traffic chart in the dashboard — one line per path. Only days that have at least one event are included; there is no zero-fill for quiet days.

Request

string

required

JWT identifying the authenticated user. Validated by the agent_user_auth_required decorator.

string

required

UUID of the agent whose path timeseries data you want.

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

Show path item properties

string

required

The API path string (e.g. /api/v1/users/).

object[]

required

Show data point properties

string

required

Date in YYYY-MM-DD format.

number

required

Number of events recorded for this path on this date.

Paths are ordered alphabetically. Dates within each path are ordered ascending. Days with zero events for a path are omitted entirely — do not assume a missing date means zero traffic.

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/path-timeseries/?start_date=2026-03-01&end_date=2026-03-07" \
  --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",
  "paths": [
    {
      "path": "/api/v1/orders/",
      "data": [
        { "date": "2026-03-01", "count": 14 },
        { "date": "2026-03-02", "count": 9 },
        { "date": "2026-03-04", "count": 22 }
      ]
    },
    {
      "path": "/api/v1/users/",
      "data": [
        { "date": "2026-03-01", "count": 10 },
        { "date": "2026-03-02", "count": 7 }
      ]
    }
  ]
}

{
  "status": 0,
  "status_description": "start_date and end_date are required"
}

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

UASAM — Users & Auth

UASAM — Projects & Keys

UASAM — Agents

Brain — Event Capture

Brain — Analytics

Get per-path event counts over time

Request

Query parameters

Response

Errors

​Request

​Query parameters

​Response

​Errors

Request

Query parameters

Response

Errors