POST `/api/v1/feeds/bundles`

Load a folder of feed files (.zip); each file needs its data:load scope.

Scope data:load:<data set>
Legacy keys
operationId dataBundle

The token needs the scope data:load:<data set>, and the person or service account behind it needs the matching privileges and account permissions, exactly as on the screens. See Scopes.

Legacy keys. Also accepts the deprecated legacy data API keys (vst_…), with Deprecation and Sunset headers. Move to a service account.

Per data set. The scope names the data set, e.g. data:load:prices. A token may load only the data sets it was given.

Request

POST /api/v1/feeds/bundles

Query parameters

Name	Required	Description
`filename`	no	The .zip (or file) name

Headers

Header	Required	Value
`Authorization`	yes	`Bearer <token>`: an OAuth access token (`vat_…`) or a personal access token (`vpt_…`), or a legacy key (`vst_…`, deprecated). Get a token
`Content-Type`	no	`application/octet-stream` (the file itself; CSV, TXT, XLSX or Vestoris XML, gzip or zip allowed)

Body

The file itself, sent as the raw request body (not a form). Name it with the filename query parameter; the extension tells Vestoris the format. See the Data Feed Reference for the XML formats and the loading center for CSV columns.

Examples

Keep the token in an environment variable (VESTORIS_TOKEN), never in the script.

curl

curl -X POST "https://vestoris.com/api/v1/feeds/bundles" \
  -H "Authorization: Bearer $VESTORIS_TOKEN" \
  -H "Content-Type: application/octet-stream" \
  --data-binary @file.csv

Python (requests)

import os, requests

r = requests.post(
    "https://vestoris.com/api/v1/feeds/bundles",
    headers={
        "Authorization": f"Bearer {os.environ['VESTORIS_TOKEN']}",
        "Content-Type": "application/octet-stream",
    },
    data=open("file.csv", "rb"),
    timeout=30,
)
r.raise_for_status()  # errors are application/problem+json with a stable "code"
print(r.json())

JavaScript (fetch)

import { readFile } from "node:fs/promises";

const res = await fetch("https://vestoris.com/api/v1/feeds/bundles", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.VESTORIS_TOKEN}`,
    "Content-Type": "application/octet-stream",
  },
  body: await readFile("file.csv"),
});
const data = await res.json();
if (!res.ok) throw new Error(`${data.code}: ${data.detail}`); // problem+json
console.log(data);

Response

201 Created, application/json: LegacyBundle. Rate-limit headers: RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset.

Response fields

Field	Type	Description
`ok`	boolean	Ok.
`bundle`	object	Bundle.
`needs_review`	list of string	Files waiting for a person on the review screen.

Example response

HTTP/1.1 201 Created
Content-Type: application/json

{
    "ok": true,
    "bundle": {},
    "needs_review": []
}

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
201	Created
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` `legacy_keys_disabled`
409	Not possible in the current state	`invalid_transition` `conflict`
413	The file is too large	`payload_too_large`
415	Unsupported file type	`unsupported_media_type`
422	The file was rejected (the batch with its row codes is in the body) or failed validation	`validation_failed`
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/bundles"
}

On the screens

The same thing in the app is explained in: