What Is a LinkedIn Profile URL Lookup?

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. Empty fields mean not found – not “try a guessed mailbox.” Invenitor’s shape: Connecting people; a 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. Recruiter language: Contact Enrichment Explained for Recruiters.

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 not: empty contact fields with a completed not-found outcome. When failing: error/timeout – not a fictional contact.

Honesty: Empty Means Not Found. Response product language: One Primary Contact, Never Invented.

Soft mesh coverage (no public hit-rate %)

Coverage varies by person and source. Soft mesh 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

Do not force a sales cloud to get a find. India desks: India Boutique IT Staffing. Builders: Adding Contact Lookup to an ATS.

Credits and billing for a lookup

1 credit only when we return an email, a phone, or both. Empty completed finds are free. Timeouts and errors do not spend. Live packs: /pricing. Deep dive: Credits, Empty Results, and Timeouts: Billing Semantics Buyers Should Demand. 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, What Is an MCP Server?, MCP for Recruiting Agents.

Desk usage in one sentence

Paste shortlisted person URLs → look up → write back only returned fields → leave empty empty → outreach on channels you already use.

Freelance: Freelance Recruiter Workflow. Contract cadence: Contract Recruiters in India. Agency sheets: Agency Desk Playbook. Screening funnel: Screening Calls Faster.

What should you do next?

Open /docs, try free lookups on real person URLs, and keep empties honest. 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”

Company pages, search URLs, expecting invent-on-empty, re-pasting the same URL without new evidence, and confusing timeout (no spend) with not found (empty, free under Credit B). Auth/rate-limit notes for product teams: REST Enrichment Inside a Hiring Product. 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. If empty, write not found. Never invent. That sentence belongs in every SOP – Contract Recruiters in India, Freelance Recruiter Workflow, Agency Desk Playbook. Agents: /mcp.md, Claude / Cursor Agents. Billing: Credits, Empty Results, and Timeouts. India commercial: INR Credit Packs, UPI to API Key. Builders: REST Enrichment Inside a Hiring Product. Screening: Screening Calls Faster. Soft mesh: contacts when we have them – no brochure hit-rate %.

Lookup vs people-search theater

A people-search UI can feel like enrichment while hiding invent-on-empty and seat tax. A LinkedIn profile URL lookup is narrower and honest: one URL, one find, explicit empty. 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. MCP definition: What Is an MCP Server?. India boutique: India Boutique IT Staffing. Primary: One Primary Contact, Never Invented. Live: /pricing · /docs.