Operations
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Catalogue only
Designed, not yet wired
These ids are in the LinkedIn catalogue but have no registry row, so they are targets rather than operations. On /v1 each answers 501 ENDPOINT_NOT_AVAILABLE at no charge; the same path under /sandbox returns a representative sample marked synthetic: true. They are listed separately so you can distinguish planned coverage from the operations available above.
/v1/linkedin/search-companies
Elsewhere
The same registry, other shapes
- LinkedIn overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=linkedin— the same rows to your code at runtime, for 0 credits.