Crustdata API / Identify people from profile URLs, emails or Google Scholar profile URLs

Resolve up to 25 identifiers to the people behind them in one synchronous request. Send exactly one identifier key: professional_network_profile_urls, emails or research_profile_urls. Profile URLs and Scholar profile URLs match exactly. Each match returns the person's crustdata_person_id, basic_profile, social_handles and updated_at; for the full profile or contact data, pass the returned profile URL to /person/enrich or /person/contact/enrich. emails accepts business and personal addresses. An address on file matches exactly. Otherwise Crustdata matches it by the name in the address at the company that owns the domain, when that match is confident enough for the company's size, and then looks it up with a contact vendor inside the same request; a match on a new address can take a few seconds longer than one already on file. The response is a top-level array with one row per identifier, in request order. match_status is matched, not_found or redacted; redacted means the person asked Crustdata to remove their data, and that row is never returned and never charged. business_emails is not accepted here; use emails. For lists larger than 25, use /batch/person/identify. Billing: 1 credit per matched identifier. Unmatched and redacted identifiers are never charged. Identify is enabled per account; without access the request returns 403. Default rate-limit is 30 requests per minute. Send an email to gtm@crustdata.co to discuss higher limits if needed for your use case.