Skip to main content
Validraft

Provider inventory

Financial Modeling Prep

Financial data API used for fundamentals, analyst data, earnings, ownership, index membership, ETF holdings, FX, crypto, macro calendar, and derivatives datasets.

FundamentalsStatic snapshotinventory 2026-06-19

Available data

What we have from Financial Modeling Prep

The broadest static snapshot in the lake: fundamentals, events, ownership, index membership, ETF holdings, FX, crypto, and COT.

Company fundamentals

annual, quarterly, TTM statementssince 2003

Analyst coverage

estimates, grades, price targets

Earnings

calendar and surprises

Ownership

13F, institutional, insider trades

Index and ETF data

constituents, delisted, holdings, weightings

FX, crypto, macro, COT

multi-asset and derivatives contextsince 1990

Raw inventory

Raw lake contents

DatasetCoverage / notePath

fundamentals

Statements annual/quarterly/TTM, approx. 2003 to 2026

same provider tree

analyst

Estimates, grades, and price targets

same provider tree

earnings

Calendar and surprises

same provider tree

corporate_actions

Dividends and split calendar

same provider tree

institutional

13F holdings, filings, and industry summary

same provider tree

insider

Insider trades

same provider tree

indexes

Index constituents and delisted records

same provider tree

macro and macro_calendar

Treasury rates and economic calendar

same provider tree

derivatives

COT report

same provider tree

FX and CRYPTO

15 FX pairs and 10 crypto assets, EOD

same provider tree

company

Profile, market cap, float

same provider tree

etf

Major ETF holdings and weightings snapshot

same provider tree

Processed / derived

Backtest-ready materializations

No separately materialized dataset is listed in the current inventory.

Validation use

  • Fundamental, factor, and event-driven validation.
  • Index membership, delisting, and ownership-aware studies.
  • Macro, FX, crypto, and derivatives context for hybrid strategies.

Notes and caveats

  • FMP News is intentionally separated because it has a different ingestion status and FinBERT processing layer.

Need this provider in a brief?

We confirm whether the existing lake is enough, whether a refresh is needed, and whether the scope depends on provider licensing before any validation run starts.