Developers › API reference › Data

GET /api/v1/schedules

Scheduled jobs and their last runs.

• Scope data:read
• operationId dataSchedules

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

Headers

Examples

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

curl "https://vestoris.com/api/v1/schedules" \
  -H "Authorization: Bearer $VESTORIS_TOKEN"

import os, requests

r = requests.get(
    "https://vestoris.com/api/v1/schedules",
    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())

const res = await fetch("https://vestoris.com/api/v1/schedules", {
  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: ScheduleList. Rate-limit headers: RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset.

Example response

HTTP/1.1 200 OK
Content-Type: application/json

{
    "data": [],
    "recent_runs": []
}

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.

{
    "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/schedules"
}

On the screens

The same thing in the app is explained in:

• Scheduled jobs