Vero Data Hub API

Request hygiene

Recommendation	Why it matters
Always use clear time ranges	Smaller responses and easier debugging
Set a reasonable `limit`	Avoids fetching more data than needed
Use cursor pagination	More stable than offset-based pagination
Cache slow-changing data	Instruments, reports and fund metadata do not need constant refetching
Retry with backoff	Avoids retry storms during temporary errors

Use case	Recommendation
Intraday charts	Query by session or day
Long history charts	Split requests into time windows
News feeds	Query by day or latest timestamp
Batch analytics	Use pagination and store progress on the client side

Send the first request

Include the limit that matches your UI or processing batch size.

Check next_cursor

If the response includes next_cursor, another page is available.

Request the next page

Send the same request with cursor set to the returned token.

Status	Suggested handling
`400`	Fix query parameters or time format
`401`	Check account credentials
`404`	Check the requested ID, symbol or code
`429`	Slow down and retry later
`503`	Retry with backoff after a short delay