Financial instrument data pay per request.
Pass in any identifier and get back a complete, cross-referenced security record on demand — no full feed to license, no nightly file to load. ISIN, CUSIP, FIGI, or ticker in; every cross-mapped identifier, asset-class and sector classifications, and corporate-actions history out. Billed per call.
Built for teams that need instrument context at the moment it matters.
Four patterns where per-call, single-instrument resolution pays for itself immediately. No feed contract, no batch window.
Resolve any identifier to all the others — on demand.
The anchor case. When reconciling a counterparty file, ingesting a trade, or matching a client position, you often have one identifier and need the rest. Pass in what you have — ISIN, CUSIP, FIGI, or ticker — and get back the complete cross-mapped set instantly. High frequency, single-instrument, naturally priced per call.
Onboard any unknown instrument the moment it arrives.
When a security first hits your order management system, portfolio system, or application, enrich it on the spot. Full identifiers, asset-class classification, sector tags, and exchange details returned in a single call — so the instrument is ready for routing, display, and reporting before the next step in the workflow.
Check any holding for corporate actions at the point of decision.
Query a single instrument for pending or historical events — splits, mergers, dividends, name changes — at the exact moment a decision or display depends on it. No batch job to schedule, no event file to parse: one call returns the corporate-actions record for that instrument, current as of the request.
Validate and classify any identifier on the fly.
Confirm that an identifier is real and currently active, then tag it with asset class and sector for compliance checks, report generation, or instrument routing. One call validates and classifies — no standing subscription to a classification service, no separate lookup against a reference file.
One identifier in, complete record out.
Your first security-master record returns in under a second. No feed contract, no onboarding call, no minimum spend — you only pay when a call returns a result.
- Billed per call
- No feed license required
The honest answers.
If something below doesn't cover your case, ping us — we answer directly, no sales process.
What identifier types does the API accept?
+
ISIN, CUSIP, FIGI, and ticker (with or without exchange qualifier). Any one of these resolves to the full cross-mapped set — so if you pass an ISIN you get back the CUSIP, FIGI, primary ticker, and all listed identifiers for that instrument.
What does a single call return?
+
Cross-mapped identifiers: ISIN, CUSIP, FIGI, primary ticker, exchange code, and all listed identifiers for the instrument. Classifications: asset class, sub-asset class, sector, industry, and country of domicile. Corporate actions: pending and historical events including splits, mergers, dividends, spin-offs, and name changes.
What if an identifier can't be matched?
+
Unmatched calls cost zero. The API returns a clear no-match response so your pipeline can branch — flag the instrument for manual review or a fallback source without paying for a failed lookup.
How is this different from licensing a full reference-data feed?
+
A feed gives you the entire universe on a recurring delivery schedule and a contract priced for that scale. This is one endpoint billed per call. If you need to resolve individual instruments on demand — at trade ingestion, at display time, at decision time — the per-call model costs a fraction of a feed for the same result.
How current is the data?
+
Corporate-actions data reflects the most recent confirmed event record. Identifier cross-mappings are refreshed continuously. For fast-moving corporate events (same-day tender offers, exchange halts), we recommend calling the API at decision time rather than caching results.
What asset classes are covered?
+
Equities, fixed income (government, corporate, municipal, agency), ETFs, mutual funds, closed-end funds, and listed derivatives across global exchanges and major OTC markets.
Can I use this inside an automated workflow or agent?
+
Yes. The endpoint is designed for agent and workflow use — single instrument in, structured record out, billed per resolved result. There is no UI requirement and no human-in-the-loop step.