Skip to main content

Look up an email

Send one email address in a JSON body with a Bearer API key. The key needs people:read or mcp:use scope. Email Lookup returns a person only when the source includes the supplied address exactly. It includes company details only when the person’s current employer is supported by the source record. A matching email domain alone does not establish employment.

Request

The address above is illustrative. Place the email in the request body, not in the URL. Do not include additional fields.

Response

The example is illustrative. Fields may be null if the source does not supply them. current_positions lists positions marked current by the provider and can contain more than one company. LinkedIn profile and company URLs are provider-supplied; the endpoint does not independently verify LinkedIn ownership or fetch a separate LinkedIn profile. match_status tells you what was established: Valid no-match requests return HTTP 200 with person: null and company: null. Role addresses such as support@ do not resolve to a person. Consumer email domains do not produce a company-only match.

Credits and errors

The endpoint makes up to three metered provider lookups. meta.credits_used reports the actual charge for the completed request: up to three credits. A completed provider lookup with no match may still consume a credit. Authentication, validation, and rate-limit rejections before provider work consume zero credits. If a later provider call fails, earlier completed lookups may remain charged. Errors use the REST error envelope and include X-Request-Id. The endpoint can return 400 for invalid input, 401 for an invalid key, 403 for insufficient scope, 429 for rate or credit limits, 500 for an internal error, or 502 for a provider failure. Use Idempotency-Key to guard against repeated billing when retrying a request; a repeated key may receive DUPLICATE_REQUEST while the first execution is pending or completed.