EODHD API: Quota Units, Coverage & Use Checklist

Data workflow

Historical market-data endpoints and other financial datasets; Marketplace products can have separate allowances.

Documented quota and access

Free documents 20 APIcalls/day. The provider distinguishes HTTP requests per minute from weighted API calls spent per day; one request can consume many calls.

Use and display boundaries

Check the selected product’s use and redistribution terms separately from its request allowance. A trial-scale free quota is not an application capacity estimate.

A practical acceptance task

Write down both request-rate and daily-call budgets for the chosen endpoints. Include bulk endpoint weights and separate Marketplace quotas before scheduling updates.

Keep the request context

Record endpoint/version, instrument identity, data frequency, timezone, history range, adjustment flags and the account entitlement. Retain only the response/provenance that the applicable terms permit. A generic provider comparison cannot replace a named dataset specification.

Test semantics before scale

Use a small authorized example and inspect status, response schema and any error object inside a successful HTTP response. Check pagination and row ordering. The local daily inspector accepts an explicitly mapped single-series CSV; it is not a universal provider JSON adapter or a certification of source accuracy.

Primary evidence

EODHD request versus call limits — checked 17 October 2026. Numeric limits are omitted where no current primary-source plan value was verified; omitted does not mean unlimited.