> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/developers/record-lookup.md). # Look up and enrich a lead with the API Use the Records API to inspect a known lead or explicitly run a supported provider lookup. ## Read what is known ```http GET /api/v1/accounts/WORKSPACE_ID/records/lookup?email=alex%40example.com Authorization: Bearer YOUR_DISTRO_API_TOKEN ``` You can supply a company `domain` instead of email. Required scope: `records:read` or `records:enrich`. The response includes available `crm`, `person`, `company`, `linkedin`, `sources` and `suggest_enrichment` values. Person/company fields are stored Distro data; an email lookup can also read a live match from the connected CRM. Lookup does not call an enrichment provider. Null person/company values mean that stored record is absent; they do not prove the prospect does not exist elsewhere. ## Read enrichment options ```http GET /api/v1/accounts/WORKSPACE_ID/records/enrichment_options ``` Required scope: `records:enrich`. Inspect available chains/providers and the maximum provider calls per lookup before choosing one. ## Enrich deliberately ```http POST /api/v1/accounts/WORKSPACE_ID/records/enrich Content-Type: application/json ``` ```json { "email": "alex@example.com", "provider": "apollo" } ``` Alternatively provide a supported `chain_id` instead of a single provider. Required scope: `records:enrich`. Observers cannot run this operation. This runs a real lookup using the workspace's credentials. The response includes `found`, `provider`, `tried`, `skipped` and resulting stored person/company fields. This is the Records sequential first-hit path, not Workflow Enrich Lead's concurrent merge. See [Provider support](/data-and-integrations/provider-support.md). The enrichment route does not expose an idempotency key contract. Avoid blind retries after a timeout; inspect current stored data and provider usage first. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/developers/record-lookup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.