· 9 min read · API
What is a LinkedIn profile URL lookup?
What is a LinkedIn profile URL lookup? A find call with a person profile URL that returns email/phone when available.
A LinkedIn profile URL lookup is a find operation: you send a person profile URL (and optionally a name), and a contact lookup API returns email, phone, or links when it has them. Invenitor’s shape: A people search and lookup API, not a sales cloud.
Category parent: What a Contact Lookup API Actually Does. Hub HowTo: LinkedIn or GitHub Profile URL → Contact Lookup API.
What goes in
- A person LinkedIn profile URL (not a company page, not a search URL, not a post permalink).
- Optional display name to help disambiguation.
- Auth: Bearer API key (/docs).
Same family: GitHub person profile URLs – GitHub Profile URL Contact Lookup.
What comes out
When found: primary email and/or phone (and links when present). When failing: error/timeout – not a fictional contact.
Coverage coverage (no public hit-rate %)
Coverage varies by person and source. Honest language is intentional: we return contacts when we have them. We do not publish hit-rate percentages. Sample your own shortlist; do not buy a brochure %.
How lookup differs from CRM and sequencers
| Layer | Job |
|---|---|
| Lookup API | URL → fields when found |
| CRM / CRM | Store people, stages, notes |
| Sequencer | Outreach automation |
Do not force a sales cloud to get a find.
Credits and billing for a lookup
1 credit only when we return an email, a phone, or both. Timeouts and errors do not spend. Live packs: /pricing. PAYG: Pay-As-You-Go Contact APIs.
REST and MCP twins
REST: POST /api/v1/find per /docs. Agents: MCP per /mcp.md – Claude / Cursor Agents: Calling a Contact Lookup MCP Endpoint,
Desk usage in one sentence
What should you do next?
Buy a pack on /pricing when ready. That is a LinkedIn profile URL lookup – not a cold-email cloud with a URL field.
Common mistakes that look like “lookup failed”
Free-plan traps: The Hidden Cost of "Free Plan" Enrichment Tools.
Teaching juniors the lookup sentence
Paste person URL. Call find. If fields exist, save them. That sentence belongs in every SOP – Agents: /mcp.md, Claude / Cursor Agents. India commercial: INR Credit Packs, Coverage: contacts when we have them – no brochure hit-rate %.
Lookup vs people-search theater
Category parent: What a Contact Lookup API Actually Does. Free-plan traps: The Hidden Cost of "Free Plan" Enrichment Tools. PAYG: Pay-As-You-Go Contact APIs. Global INR rail: US Price Arbitrage. Live: /pricing · /docs.
Questions
What is a LinkedIn profile URL lookup?
A find call with a person LinkedIn profile URL that returns email/phone when available.
Can I use a company page URL?
No. Use person profile URLs. Company pages are the wrong input.
When does a credit spend?
1 credit only when we return an email, a phone, or both. Timeouts and errors do not spend.
Is GitHub supported the same way?
Yes – person GitHub profile URLs on the same find path.
Where are REST and MCP docs?
/docs for REST and /mcp.md for agents.
How is this different from a CRM?
Lookup resolves fields from a URL. A CRM stores workflow. Invenitor is not a sales cloud.
