Skip to main content
A company is identified differently by everyone who tracks it: LinkedIn by a slug, the SEC by a CIK, an exchange by a ticker, a sales tool by its domain, Wikidata by a QID. The external-links endpoint returns every one of those in a single shape — the platform, the platform-native identifier, and a ready-to-use URL where one exists.
This page is the forward index: given a company, list every identifier we hold for it. To go the other way — given a LinkedIn slug, domain, ticker, or CIK, find the matching company, in bulk — use GET /v1/entities/lookup.
Use this endpoint when you want to:
  • Enrich your own company records with identifiers you do not yet hold.
  • Join Particle companies to a dataset keyed by LinkedIn, ticker, or CIK.
  • Build a “find this company on…” UI without per-platform URL templates.
Identify the company by slug, domain, or ID.
Every identifier here is accepted by GET /v1/entities/lookup, so the two endpoints round-trip.

Platforms

A company can carry several tickers — a dual-listed or multi-class company holds one row per symbol. Every other platform is one identifier per company.Symbols are read live from the company’s ticker records rather than stored alongside the other identifiers, so they are never stale.

Behavior and edge cases

Identifiers also appear inline on the company

GET /v1/companies/{id} returns the same list as external_links alongside the company, so fetching a single company does not need a second call. The list endpoint GET /v1/companies omits it.

url is absent where no canonical page exists

A ticker symbol identifies a company but has no single web page that represents it, so those rows carry an identifier and no URL.

Discovery is asynchronous

Identifiers that come from a company’s own record — domain, ticker, CIK, QID — are present as soon as the company is. Social profiles are discovered separately, so a newly created company may not carry them yet.