REST API Endpoints for Argus Performance Data

The performance API exposes aggregated transaction timings and web vitals collected by the browser SDK (@argusdev/sdk-browser ≥ 0.2). Both endpoints aggregate over a bounded time window you control with the days query parameter.

Authentication

Both endpoints require an active session. Requests without a valid session cookie return 401 Unauthorized.

Query Parameters (both endpoints)

days

number

default:"7"

Aggregation window in days. Allowed range 1–30.

List Transactions

Returns transactions grouped by name, with percentile durations computed over the window (up to the most recent 5,000 rows). Sorted by count descending, top 50 groups.

GET /api/v1/projects/:projectId/performance/transactions

projectId

string

required

The ID of the project whose transactions you want to retrieve.

Example Request

curl "https://your-domain.com/api/v1/projects/clxk2m9ab0000qw8e3f7t1pz2/performance/transactions?days=7" \
  -H 'Cookie: session=YOUR_SESSION_COOKIE'

Example Response

{
  "statusCode": 200,
  "status": "success",
  "message": "Transactions fetched successfully",
  "data": [
    {
      "name": "page.load /dashboard",
      "count": 128,
      "p50": 940,
      "p75": 1480,
      "p95": 3210,
      "lastSeen": "2026-07-06T09:31:41.041Z"
    }
  ]
}

Durations are in milliseconds.

Get Web Vitals

Returns the p75 (web-vitals reporting standard) for each core vital across the window, with a rating per web.dev thresholds and the number of samples behind it. A vital with no samples is null.

GET /api/v1/projects/:projectId/performance/vitals

projectId

string

required

The ID of the project whose web vitals you want to retrieve.

Example Request

curl "https://your-domain.com/api/v1/projects/clxk2m9ab0000qw8e3f7t1pz2/performance/vitals?days=7" \
  -H 'Cookie: session=YOUR_SESSION_COOKIE'

Example Response

{
  "statusCode": 200,
  "status": "success",
  "message": "Web vitals fetched successfully",
  "data": {
    "vitals": {
      "lcp": { "p75": 2140, "rating": "good", "samples": 118 },
      "cls": { "p75": 0.06, "rating": "good", "samples": 112 },
      "fcp": { "p75": 1650, "rating": "good", "samples": 118 },
      "ttfb": { "p75": 410, "rating": "good", "samples": 120 }
    },
    "sampleCount": 120
  }
}

rating is one of good, needs-improvement, or poor. LCP/FCP/TTFB are in milliseconds; CLS is unitless.

Response Codes

Status	Meaning
`200`	Request succeeded.
`401`	Not authenticated — no valid session.
`404`	Project not found, or not in your organization.

​Authentication

​Query Parameters (both endpoints)

​List Transactions

​Example Request

​Example Response

​Get Web Vitals

​Example Request

​Example Response

​Response Codes

Authentication

Query Parameters (both endpoints)

List Transactions

Example Request

Example Response

Get Web Vitals

Example Request

Example Response

Response Codes