Developers › API reference › Data
GET /api/v1/feeds/runs
Feed runs of a business date.
- Scope
data:read - operationId
dataFeedRuns
The token needs the scope data:read, and the person or service account behind it needs the matching privileges and account permissions, exactly as on the screens. See Scopes.
Request
GET /api/v1/feeds/runs
Query parameters
| Name | Required | Description |
|---|---|---|
date | no | YYYY-MM-DD (default: today's business date) |
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/feeds/runs" \
-H "Authorization: Bearer $VESTORIS_TOKEN"
Python (requests)
import os, requests
r = requests.get(
"https://vestoris.com/api/v1/feeds/runs",
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/feeds/runs", {
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: FeedRunList. Rate-limit headers: RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset.
Response fields
| Field | Type | Description |
|---|---|---|
business_date | string | The business date the data is for (YYYY-MM-DD). |
data | list of FeedRun | The records of this page or list. |
data[].id | id (string) or null | The record's id (a string of digits). |
data[].feed_id | id (string) | The feed's id. |
data[].feed | string | The feed's name. |
data[].dataset | string | The data set: securities, accounts, positions, lots, cash, prices, fx, corporate_actions, issuers, brokers, benchmarks… |
data[].status | string | expected, arrived, applied, held, rejected, late or missed. |
data[].file_name | string | The file's name. |
data[].batch_id | id (string) or null | The id of the data batch that made it. |
data[].rows | integer | Number of rows. |
data[].code | string | The result code (see the Data Feed Reference). |
data[].message | string | A message in plain words. |
data[].arrived_at | date-time or null | When the feed file arrived. |
data[].finished_at | date-time or null | When it finished. |
Example response
HTTP/1.1 200 OK
Content-Type: application/json
{
"business_date": "2026-10-27",
"data": [
{
"id": null,
"feed_id": "4",
"feed": "Morning prices",
"dataset": "prices",
"status": "applied",
"file_name": "ACME_PRICE_20261027_001.xml",
"batch_id": "311",
"rows": 612,
"code": "OK",
"message": "",
"arrived_at": "2026-10-27T14:30:00Z",
"finished_at": null
}
]
}
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/feeds/runs"
}
On the screens
The same thing in the app is explained in: