/pagesjaunes/businesses

POST /api/pagesjaunes/businesses

Price: 10 credits

Get a PagesJaunes business (professional) by its numeric id

How to use it

Get full PagesJaunes business details by numeric id (from a /pros/{id} URL). Returns name, activities, description, phone numbers, address with coordinates, website, social links, PagesJaunes rating and review count, partner ratings (Tripadvisor, Google), price range, cuisine, payment methods, opening schedule, photos, AI-analysed review aspects, and legal/registration info (SIREN, SIRET, NAF code, legal form).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• business string required — PagesJaunes business id, or the full /pros/{id} URL (examples: "51616827"; minLength: 1)

Response

• @type string (default: "PagesJaunesBusiness")
• id string required
• url string required
• name string required
• business_type string nullable
• description string nullable
• phone string nullable
• phones array (default: [])
• address object nullable
  • @type string (default: "PagesJaunesAddress")
  • street string nullable
  • postal_code string nullable
  • city string nullable
  • country string nullable
• latitude number nullable
• longitude number nullable
• rating number nullable
• review_count integer nullable
• partner_ratings array (default: [])
  • @type string (default: "PagesJaunesPartnerRating")
  • provider string required
  • rating number nullable
  • review_count integer nullable
• price_range string nullable
• cuisine string nullable
• payment_methods array (default: [])
• image string nullable
• images array (default: [])
• website_url string nullable
• socials object (default: {})
  • * string
• schedule array (default: [])
  • @type string (default: "PagesJaunesScheduleDay")
  • day string required
  • hours array (default: [])
• activities array (default: [])
• legal object nullable
  • @type string (default: "PagesJaunesLegalInfo")
  • siren string nullable
  • siret string nullable
  • naf_code string nullable
  • legal_form string nullable
  • creation_date string nullable
  • establishment_workforce string nullable
  • company_workforce string nullable
  • establishment_type string nullable
  • other_names string nullable
• ai_aspects array (default: [])
  • @type string (default: "PagesJaunesReviewAspect")
  • name string required
  • positive_count integer nullable
  • neutral_count integer nullable
  • negative_count integer nullable
  • total_count integer 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 — Business not found for the given id 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.