Finance · head-to-head
OpenFIGI vs SEC EDGAR Data
OpenFIGI is Bloomberg's free public API for the Financial Instrument Global Identifier (FIGI) standard, mapping third-party symbology (tickers, ISINs, CUSIPs, SEDOLs) to FIGIs across equities, options, futures, and indices, plus full-text search and a bulk spreadsheet-upload tool. A live test of the mapping endpoint returned real data with zero API key supplied, capped at 25 requests per 60 seconds — the entry's stored `API Key` auth is corrected to `None`, since registering for a free key only raises that throughput ceiling rather than gating access. A live Origin-header probe (an OPTIONS preflight and a real POST) found no Access-Control-Allow-Origin header on either response, correcting the stored `cors: yes` to `no`.
SEC EDGAR's data.sec.gov REST APIs serve JSON-formatted company filing histories and XBRL financial-statement facts (10-K, 10-Q, 8-K, and more) extracted from filings submitted to the U.S. Securities and Exchange Commission. No authentication or API key is required, but the SEC's fair-access policy requires a descriptive User-Agent header identifying the requester and caps traffic at 10 requests per second — requests without one are rejected with a 403. A live probe confirmed CORS is enabled (Access-Control-Allow-Origin: *) once that header is set.
| OpenFIGI | SEC EDGAR Data | |
|---|---|---|
| Authentication | None | None |
| Pricing | free | free |
| Formats | JSON | JSON |
| CORS | no | yes |
| HTTPS | Yes | Yes |
SEC EDGAR Data supports CORS, while OpenFIGI doesn't — pick SEC EDGAR Data for direct browser calls.