/pagesjaunes/people/search

POST /api/pagesjaunes/people/search

Price: 5 credits

Search PagesJaunes white pages by name, or reverse-lookup a phone number

How to use it

Search the PagesJaunes white pages (PagesBlanches) for individuals by name with an optional location, or pass a phone number as the query to perform a reverse lookup and find who owns it. Returns name, address, and phone number(s); business entries also include their activity and a link to the full business profile.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• quoiqui string required — A person's name, or a phone number for reverse lookup (examples: "Martin", "0140474000"; minLength: 1)
• count integer required — Max number of results (min: 1)
• ou string nullable — Where: city or address (optional, ignored for reverse phone lookup)
• sort string — Result ordering (default: "relevance"; one of: "relevance", "az", "za")

Response

• @type string (default: "PagesJaunesPerson")
• name string required
• address string nullable
• postal_code string nullable
• city string nullable
• phone string nullable
• phones array (default: [])
• is_business boolean (default: false)
• activity string nullable
• url string nullable

Errors

• 422 — The request body did not validate 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 — The entity was not found, or a precondition failed 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.