CUSIP, ISIN and FIGI on Every Row: Symbology Mapping in the Bourse API

Why funds need CUSIP, ISIN and FIGI instead of company names, where Bourse gets each identifier and how to look one up with /v1/symbology.

Public filings name companies inconsistently: "Alphabet Inc.", "Google", GOOG, GOOGL. Fund systems join data on CUSIP, ISIN or FIGI. The Bourse API now returns all of them on every record that has a ticker.

Key takeaways

• Every record with a ticker carries cik, cusip, isin and figi.
• CIK comes from the SEC company list, CUSIP from Form 13F filings, ISIN is computed from the CUSIP with the standard check digit, and FIGI comes from OpenFIGI.
• GET /v1/symbology?ticker=AAPL (or cusip=, isin=, figi=, cik=) returns the full mapping for one security.
• The mapping refreshes daily.

Example

``` GET /v1/symbology?isin=US0378331005

{ "ticker": "AAPL", "cik": "0000320193", "cusip": "037833100", "isin": "US0378331005", "figi": "BBG000B9XRY4" } ```

Why it matters

Without identifiers, a data team writes and maintains its own name-matching code, and every mismatch silently drops rows. With them, Bourse data joins directly to a security master, a risk system or a warehouse table.

Coverage is broad for U.S. listed stocks; a few small issuers without 13F holders have no CUSIP yet. See the API reference and the developer page.

Bourse provides financial data and editorial information, parts of which are generated by AI. This page is for general education only. It is not personalised investment advice or a recommendation to buy or sell any financial instrument. Make your own decisions.