EOD Historical Data · Rate Limits

Eod Historical Rate Limits

EODHD enforces a daily API call quota that resets at midnight GMT and a per-minute burst cap. The free tier is limited to 20 calls/day. All paid plans share a 100,000 calls/day quota and 1,000 requests/minute burst limit. Requests that exceed the daily quota return an HTTP 429 response. Daily counts and remaining limits are reported via the /api/user endpoint. There is no per-second cap documented; the 1,000 rpm cap applies uniformly across all paid tiers.

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

It captures 4 rate-limit definitions, measuring requests_per_day and requests_per_minute.

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

Tagged areas include Fintech, Market Data, and Rate Limiting.

4 Limits Throttle: 429
FintechMarket DataRate Limiting

Limits

Free daily quota api_key
requests_per_day
20
Free tier; resets midnight GMT.
Free per-minute cap api_key
requests_per_minute
1000
Free tier burst cap.
Paid daily quota api_key
requests_per_day
100000
Applies to all paid plans (EOD All World, Intraday, Fundamentals, All-In-One). Resets midnight GMT.
Paid per-minute cap api_key
requests_per_minute
1000
Applies to all paid plans; sustained burst limit.

Policies

Daily Reset
API call counters reset at midnight GMT. The exact reset time can be tracked via the apiRequestsDate field returned by the /api/user endpoint.
Quota Monitoring
Remaining daily quota can be inspected at any time via GET https://eodhd.com/api/user?api_token={token}&fmt=json. The response fields apiRequests and dailyRateLimit expose current usage and the cap. The extraLimit field shows additionally purchased call credits.
Extra Credits
Additional API calls can be purchased on top of any paid plan to handle temporary spikes. The remaining extra credits are visible in the extraLimit field of the User API response.
Backoff Strategy
Implement exponential backoff with jitter when HTTP 429 responses are received. For batch workflows, spread requests evenly across the day to stay below the 1,000 rpm cap. Each historical endpoint call counts as 1 API call regardless of the date range requested.

Sources