Person Info
Resolve a person from any handle you hold — an email, a LinkedIn URL, a provider id — into a full profile with work email, title and employer
Endpoint
One endpoint for every offer below. Omit provider and the router picks with automatic failover — the response's served_by tells you which one ran.
https://api.socialrouter.io/v1/enrich/person/infoOffers
Every offer below returns the same normalized output, in failover order — the first one serves unless you pin another with the provider field.
apollo/personvia Apollodefault routeUp to 10 identifiers per request
your own keyyou bring it
Parameters
JSON body of the request. Unknown fields and unknown options are rejected with the valid list, so a wrong guess costs nothing.
| Parameter | Type | Description |
|---|---|---|
identifiersRequired | string[] | One URL per record to process. Accepted shapes:<email> — The strongest match key — use it whenever you have one.https://www.linkedin.com/in/<handle><provider_id> — A provider-side record id, as returned by person/search.Example: alexandre@trustlist.aiA single url string is accepted too. |
providerOptional | string | Pin one offer, e.g. apollo/person. Omit it and the router picks with failover. |
limitOptional | integer | Max records to return per URL. |
optionsOptional | object | Service-specific options, listed below. |
options.revealPersonalEmailsOptional | boolean | Also return personal email addresses. Consumes extra credits on your own provider account. Defaults to false. |
Going further
Auth, error semantics, and every other endpoint live in the API reference — including the machine-readable OpenAPI spec at /v1/openapi.json.
Frequently asked questions
How much does Person info cost?
SocialRouter bills nothing per record for this service: every offer runs on a provider key you register yourself, and the records are invoiced to you by that provider directly.
Which offers serve person/info?
apollo/person — 1 offer is available behind the same endpoint. Pin one with the optional "provider" field, or omit it and the router picks with automatic failover. The response's "served_by" field names the offer that ran.
What input does it need?
The "identifiers" field of the JSON body, as an array of strings: <email> — The strongest match key — use it whenever you have one.; or https://www.linkedin.com/in/<handle>; or <provider_id> — A provider-side record id, as returned by person/search.. For example: alexandre@trustlist.ai
Is the output format the same for every offer?
Yes. Every offer returns the normalized record schema documented on this page; some add extra platform-specific fields on top, but the documented fields are always present.
How many identifiers can I send per request?
Up to 10 identifiers in a single request, depending on the offer.
What happens if an offer fails?
SocialRouter automatically fails over to the next offer serving the same service, so a single upstream outage doesn't break your integration.
What options does it take?
revealPersonalEmails (boolean): Also return personal email addresses. Consumes extra credits on your own provider account.