/resolve/people/search

POST /api/resolve/people/search

Price: 20 credits

People matching a name and a company or location, best match first, each with the records our sources hold, the person's identifiers and the follow-up calls worth making next.

How to use it

Use when you hold a person's name and know their company or location; for a profile URL or an identifier use resolve/people. Returns up to count people ordered best first. A match with an id opens next with the resolve/people call for it; pass its params as-is.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• name string required — Full name of the person (examples: "Linus Torvalds"; minLength: 1)
• company string nullable — Company the person works at now (examples: "Linux Foundation")
• location string nullable — City or region the person lives in (examples: "San Francisco")
• count integer required — Max number of people to return (min: 1; max: 100)

Response

• @type string (default: "PersonMatch")
• id string nullable — Strongest identifier of the person that resolve/people takes, as type:value; null when its records carry none (examples: "linkedin_user:linustorvalds")
• name string required — Name as the best-matching record gives it (examples: "Linus Torvalds")
• strong boolean required — The name matches exactly and the record comes from a source that applied the given company or location
• links array — Search records describing this person (default: [])
  • @type string (default: "MatchedRecord")
  • source string required — Platform the record comes from (examples: "sitejabber")
  • endpoint string required — Search endpoint that returned the record, callable as it is (examples: "sitejabber/businesses/search")
  • record object required — The record exactly as that endpoint returns it
  • partial boolean — The source stopped before it answered in full (default: false)
• identifiers object — Every identifier of the person found in the records, by type: the primary value, the platforms carrying it and the other values found (default: {})
  • * object
    • @type string (default: "ResolvedIdentifier")
    • value string required — Identifier value (examples: "stripe.com")
    • sources array required — Platforms whose records carry this value
    • alternatives array — Other values of the same identifier carried by the records, most carried first (default: [])
      • @type string (default: "IdentifierValue")
      • value string required — Identifier value (examples: "stripe.com")
      • sources array required — Platforms whose records carry this value
• not_found object — Endpoints checked that gave no record, grouped by why
  • @type string (default: "NotFound")
  • no_record array — Endpoints that answered without a record (default: [])
  • error array — Endpoints that failed to answer (default: [])
  • timeout array — Endpoints that ran out of their time budget (default: [])
  • skipped array — Endpoints that do not take the identifier they were given (default: [])
• next array — Follow-up calls for this person, most used first, each with its payload filled in; when id is set, it opens with the resolve/people call for that id (default: [])
  • @type string (default: "NextCall")
  • endpoint string required — Endpoint to call next (examples: "webparser/render")
  • params object required — Its payload, ready to send (examples: {"url":"https://stripe.com"})

Errors

• 422 — name is empty, or neither company nor location is given. Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No person matching the name was found. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.