Data catalog / enrichment

Enrichment data

Detailed profile data for a LinkedIn person URL — the core enrichment endpoint.

Last updated September 23, 2026

How it works

Pass a LinkedIn profile URL and get back structured fields — name, headline, summary, industry, location, and more. This is the endpoint underneath most enrichment workflows on RichAPI: search finds the people, this fills in the details.

When to use it

Run it on a single URL for an ad hoc lookup, or use enrich_profiles_bulk when you already have a batch of up to 50 URLs — bulk is more efficient than calling this endpoint in a loop.

Reference

urlstring · Required
LinkedIn profile URL.
useCacheboolean · Optional
Use cached data (up to 24h). Defaults to true.

Request

Minimum required parameters for a enrichment data call.

Request
{
  "url": "https://www.linkedin.com/in/satyanadella"
}

See it in a workflow

Playbooks

Real patterns, recipes, and prompts other builders run on RichAPI

Start free with 25 credits

Developer Docs

Auth, request shape, and error handling

See Documentation

FAQ

Frequently asked questions

Detailed profile data for a LinkedIn person URL — the core enrichment endpoint.
Every endpoint is billed from the same credit pool, at the published rate on /pricing — never a separate contract per endpoint.
Yes — the same endpoint is reachable from an MCP client (Claude, ChatGPT, Cursor, Windsurf) using the same key and credit pool. See /mcp.

Related data