GET `/api/v1/batches`

Load history.

Scope data:read
operationId dataBatches

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.

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/batches

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
`dataset`	no	Data set
`status`	no	staged, held, applied, undone, rejected

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/batches?dataset=prices&status=staged" \
  -H "Authorization: Bearer $VESTORIS_TOKEN"

Python (requests)

import os, requests

r = requests.get(
    "https://vestoris.com/api/v1/batches",
    headers={
        "Authorization": f"Bearer {os.environ['VESTORIS_TOKEN']}",
    },
    params={
        "dataset": "prices",
        "status": "staged"
    },
    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/batches?dataset=prices&status=staged", {
  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 Batch. Rate-limit headers: RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset.

Response fields

Field	Type	Description
`data`	list of Batch	The records of this page.
`data[].id`	id (string)	The record's id (a string of digits).
`data[].dataset`	string	The data set: securities, accounts, positions, lots, cash, prices, fx, corporate_actions, issuers, brokers, benchmarks…
`data[].status`	string	staged, held, applied, undone, rejected or discarded.
`data[].source`	string	upload, feed, api, bundle or ai_suggestion.
`data[].mode`	string	"upsert" (default) or "full" (records missing from the file are inactivated).
`data[].file_name`	string	The file's name.
`data[].sha256`	string	SHA-256 of the file.
`data[].business_date`	date or null	The business date the data is for (YYYY-MM-DD).
`data[].counts`	object	Rows by outcome: new, changed, unchanged, rejected, deleted.
`data[].message`	string	A message in plain words.
`data[].hold_reason`	string or null	Why the batch is held for review.
`data[].created_at`	date-time or null	When it was created.
`data[].applied_at`	date-time or null	When it was applied.
`data[].undone_at`	date-time or null	When it was undone.
`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",
            "dataset": "prices",
            "status": "staged",
            "source": "api",
            "mode": "upsert",
            "file_name": "ACME_PRICE_20261027_001.xml",
            "sha256": "e3b0…",
            "business_date": "2026-10-27",
            "counts": {
                "new": 3,
                "changed": 12,
                "unchanged": 580,
                "rejected": 1
            },
            "message": "",
            "hold_reason": null,
            "created_at": "2026-10-27T14:30:00Z",
            "applied_at": "2026-10-27T14:30:00Z",
            "undone_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/batches"
}

On the screens

The same thing in the app is explained in:

Load history