Financial Modeling Prep · Rate Limits

Financialmodelingprep Rate Limits

Financial Modeling Prep enforces two overlapping limits on the REST API: a request-rate cap and a trailing 30-day bandwidth allowance, both scaling with plan tier. The free Basic tier is capped at 250 requests per day. Paid tiers are governed by a per-minute request rate - approximately 300 requests/minute on Starter, 750 on Premium, and 3000 on Ultimate - and a rolling 30-day bandwidth budget of roughly 500 MB (free), 20 GB (Starter), 50 GB (Premium), and 150 GB (Ultimate). Exceeding a limit returns an HTTP 429 response.

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

It captures 5 rate-limit definitions, measuring requests and bytes.

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

Tagged areas include Financial Data, Market Data, Rate Limiting, Quotas, and Bandwidth.

5 Limits Throttle: 429
Financial DataMarket DataRate LimitingQuotasBandwidth

Limits

Free Daily Requests account
requests
250 per day
Basic (free) tier cap on total requests per calendar day.
Starter Request Rate account
requests
~300 per minute
Per-minute request cap on the Starter tier.
Premium Request Rate account
requests
~750 per minute
Per-minute request cap on the Premium tier.
Ultimate Request Rate account
requests
~3000 per minute
Per-minute request cap on the Ultimate tier.
Bandwidth Allowance account
bytes
500MB / 20GB / 50GB / 150GB (Free / Starter / Premium / Ultimate)
Trailing 30-day bandwidth budget per plan tier.

Policies

Throttling
Requests beyond the plan's rate or bandwidth allowance receive an HTTP 429 response.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and spread bulk pulls across time to stay within the 30-day bandwidth budget.
Bulk And Caching
Use bulk endpoints and client-side caching of slowly-changing fundamentals to reduce request volume and bandwidth consumption.

Sources