Resolve a hashed email (HEM), plain email address, or LinkedIn profile URL to stored identity data. Provide exactly one of hem, email, or linkedin_url.

Hash type. A hem is matched by algorithm: SHA-256 (64 hex characters) or MD5 (32 hex characters). The algorithm is inferred from the digest length; pass hem_type to set it explicitly (it is then validated against the hem). When email is provided instead, it is normalized and hashed for you. LinkedIn. linkedin_url accepts any pasted shape of a personal profile URL (linkedin.com/in/<slug>, with or without a scheme, www. or a locale subdomain, a trailing slash, ?trk= parameters, or deeper path segments). It is reduced to the vanity slug and resolved to the same record an email lookup returns. Company, school, and legacy /pub/ URLs are rejected with 400. hem_type does not apply.

Filtering and projection. Optional filter and select params apply the same grammar as /api/v3/events/{tier}, evaluated against the single resolved record:

• select projects a subset of fields (comma-separated). Absent fields are omitted.
• filter (<field>:<op>:<value>, , = AND, | = OR within a group; ops eq, ne, like, not_null) decides whether the record is returned. If the record does not match, the endpoint responds 404 (no record). Example — business-email records only: filter=current_business_email:ne:""|business_emails:ne:""|is_email_business:eq:"true". Quote literal values (is_email_business:eq:"true").

Billing. Metered on egress as contact_record (the same meter as a contact query or audience download, not the events resolution_* tiers): a 200 that returns a record bills one contact record; a 404 (not found or filtered out) bills nothing. select projects fields but does not change the meter.