Developers › API reference › Surveillance
GET /api/v1/surveillance/alerts
Surveillance and anomaly alerts.
- Scope
surveillance:read - operationId
complianceAlerts
The token needs the scope surveillance:read, and the person or service account behind it needs the matching privileges and account permissions, exactly as on the screens. See Scopes.
Paginated. Cursor pagination: limit (1 to 200, default 50); pass next_cursor as cursor until has_more is false. fields= returns only the named fields.
Request
GET /api/v1/surveillance/alerts
Query parameters
| Name | Required | Description |
|---|---|---|
limit | no | Page size, 1 to 200 (default 50) |
cursor | no | The next_cursor of the previous page |
sort | no | "-id" (newest first, default) or "id" |
fields | no | Sparse fieldset: comma-separated field names |
kind | no | surveillance, cross_component, access or orders |
status | no | open, reviewed, dismissed, escalated |
Headers
| Header | Required | Value |
|---|---|---|
Authorization | yes | Bearer <token>: an OAuth access token (vat_…) or a personal access token (vpt_…). Get a token |
Examples
Keep the token in an environment variable (VESTORIS_TOKEN), never in the script.
curl
curl "https://vestoris.com/api/v1/surveillance/alerts" \
-H "Authorization: Bearer $VESTORIS_TOKEN"
Python (requests)
import os, requests
r = requests.get(
"https://vestoris.com/api/v1/surveillance/alerts",
headers={
"Authorization": f"Bearer {os.environ['VESTORIS_TOKEN']}",
},
timeout=30,
)
r.raise_for_status() # errors are application/problem+json with a stable "code"
print(r.json())
JavaScript (fetch)
const res = await fetch("https://vestoris.com/api/v1/surveillance/alerts", {
method: "GET",
headers: {
Authorization: `Bearer ${process.env.VESTORIS_TOKEN}`,
},
});
const data = await res.json();
if (!res.ok) throw new Error(`${data.code}: ${data.detail}`); // problem+json
console.log(data);
Response
200 OK, application/json: a page of Alert. Rate-limit headers: RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset.
Response fields
| Field | Type | Description |
|---|---|---|
data | list of Alert | The records of this page. |
data[].id | id (string) | The record's id (a string of digits). |
data[].kind | string | surveillance, cross_component, access or orders. |
data[].severity | string | How serious: for rules "block", "warn" or "info"; for alerts and issues "high", "medium" or "low". |
data[].status | string | open, reviewed, dismissed or escalated. |
data[].summary | string | What was detected. |
data[].details | object | Structured details. |
data[].suggested_fix | string | A suggested fix (applied only by a person). |
data[].narrative | string or null | A narrative written from the facts (by the AI when it is on). |
data[].narrative_by_ai | boolean | True when the AI wrote the narrative. |
data[].user_id | id (string) or null | The user. |
data[].account_id | id (string) or null | The account's id. |
data[].order_id | id (string) or null | The order's id. |
data[].security_id | id (string) or null | The security's id. |
data[].review_note | string | The reviewer's note. |
data[].reviewer_id | id (string) or null | Who reviewed it. |
data[].created_at | date-time or null | When it was created. |
data[].reviewed_at | date-time or null | When it was reviewed. |
next_cursor | string or null | Pass as ?cursor= for the next page; null on the last page. |
has_more | boolean | True when another page follows. |
Example response
HTTP/1.1 200 OK
Content-Type: application/json
{
"data": [
{
"id": "1042",
"kind": "surveillance",
"severity": "warn",
"status": "open",
"summary": "Possible wash trade: MSFT bought and sold within 3 days across GRW-A and GRW-B",
"details": [],
"suggested_fix": "",
"narrative": null,
"narrative_by_ai": false,
"user_id": "7",
"account_id": "12",
"order_id": "5301",
"security_id": "3",
"review_note": "",
"reviewer_id": null,
"created_at": "2026-10-27T14:30:00Z",
"reviewed_at": null
}
],
"next_cursor": "eyJpZCI6NTI5OX0",
"has_more": true
}
Example values. Your values depend on your firm's data; prices, orders and fills are simulated.
Status codes and errors
Errors are application/problem+json (RFC 9457) with a stable code to program against; the detail says what to fix. See Errors.
| Status | When | Problem codes |
|---|---|---|
| 200 | Success | |
| 400 | The request is malformed | invalid_request |
| 401 | No token, or it is invalid or expired | invalid_token |
| 403 | The token lacks the scope, or the person or service account behind it lacks the privilege or account permission | insufficient_scope forbidden ip_not_allowed |
| 429 | Rate limited: wait for Retry-After seconds | rate_limited |
{
"type": "https://vestoris.com/developers/errors#validation_failed",
"title": "Validation failed",
"status": 422,
"detail": "Quantity must be greater than zero.",
"code": "validation_failed",
"instance": "/api/v1/surveillance/alerts"
}
On the screens
The same thing in the app is explained in: