Barchart · Rate Limits

Barchart Rate Limits

Barchart OnDemand does not publish fixed numeric request-rate limits. Usage is governed by the entitlements in your subscription or enterprise package - which endpoints, asset classes, symbols, and data timeliness you are licensed for - rather than by a single public per-minute cap. Two documented behaviors do shape responses - default result sets are capped at 20 records unless a `maxRecords` parameter is supplied, and intraday data may be delayed by up to ~20 minutes on some tiers due to caching. Some datasets (for example futures options) refresh only at scheduled times during the day.

Barchart Rate Limits is the machine-readable rate-limit profile for Barchart on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, records, entitlement, and latency.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Market Data, Financial Data, Commodities, Reference Data, and Rate Limiting.

4 Limits Throttle: 429
Market DataFinancial DataCommoditiesReference DataRate LimitingQuotas

Limits

Request Rate apikey
requests
not published (per-contract entitlement)
No fixed public per-minute request cap; governed by subscription/enterprise terms.
Default Result Cap request
records
20 (unless maxRecords is set)
Results default to 20 records per call unless the maxRecords parameter increases it.
Symbol / Endpoint Entitlement apikey
entitlement
per package
Access to specific endpoints, asset classes, and symbols is scoped by your licensed package.
Data Timeliness apikey
latency
real-time / delayed / end-of-day per entitlement
Intraday data may be delayed up to ~20 minutes on some tiers; real-time requires exchange licensing.

Policies

Scheduled Refresh
Some datasets (e.g. getFuturesOptions) update only at scheduled intervals during the day rather than continuously.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Pagination via maxRecords
Use the maxRecords parameter (and date ranges on history endpoints) to bound response size instead of relying on the 20-record default.

Sources