/sirene/companies/nearby

POST /api/sirene/companies/nearby

Price: 20 credits

Find French companies with an establishment within a radius of a geographic point

How to use it

Find French companies that have an establishment within a given radius (km) of a latitude/longitude point. Returns full registry details per company, nearest first. Use the 'search' endpoint for name/keyword search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• lat number required — Latitude of the search point (examples: 48.8566; min: -90; max: 90)
• long number required — Longitude of the search point (examples: 2.3522; min: -180; max: 180)
• radius number required — Search radius in kilometres (examples: 1; min: 0.001; max: 50)
• count integer required — Max number of companies to return (min: 1; max: 10000)

Response

• @type string (default: "SireneCompany")
• siren string required
• name string required
• legal_name string nullable
• sigle string nullable
• status string nullable
• legal_form string nullable
• company_category string nullable
• section_activite_principale string nullable
• activite_principale string nullable
• activite_principale_naf25 string nullable
• workforce_range string nullable
• annee_tranche_effectif_salarie string nullable
• establishment_count integer nullable
• open_establishment_count integer nullable
• creation_date string nullable
• closure_date string nullable
• updated_at string nullable
• statut_diffusion string nullable
• headquarters object nullable
  • @type string (default: "SireneEstablishment")
  • siret string required
  • is_headquarters boolean (default: false)
  • status string nullable
  • activite_principale string nullable
  • activite_principale_naf25 string nullable
  • address string nullable
  • street_number string nullable
  • street_type string nullable
  • street_name string nullable
  • postal_code string nullable
  • commune string nullable
  • city string nullable
  • departement string nullable
  • region string nullable
  • epci string nullable
  • latitude string nullable
  • longitude string nullable
  • creation_date string nullable
  • activity_start_date string nullable
  • closure_date string nullable
  • workforce_range string nullable
  • nom_commercial string nullable
  • enseignes array
• officers array
  • @type string (default: "SireneOfficer")
  • type_dirigeant string nullable
  • qualite string nullable
  • nom string nullable
  • prenoms string nullable
  • annee_de_naissance string nullable
  • date_de_naissance string nullable
  • nationalite string nullable
  • siren string nullable
  • denomination string nullable
• finances array
  • @type string (default: "SireneFinance")
  • year string required
  • ca integer nullable
  • resultat_net integer nullable
• complements object nullable
  • @type string (default: "SireneComplements")
  • is_association boolean (default: false)
  • is_entrepreneur_individuel boolean (default: false)
  • is_ess boolean (default: false)
  • is_societe_mission boolean (default: false)
  • is_service_public boolean (default: false)
  • is_administration boolean (default: false)
  • is_rge boolean (default: false)
  • is_bio boolean (default: false)
  • is_finess boolean (default: false)
  • is_qualiopi boolean (default: false)
  • is_organisme_formation boolean (default: false)
  • is_entrepreneur_spectacle boolean (default: false)
  • is_achats_responsables boolean (default: false)
  • is_alim_confiance boolean (default: false)
  • is_patrimoine_vivant boolean (default: false)
  • is_siae boolean (default: false)
  • is_uai boolean (default: false)
  • is_avocat boolean (default: false)

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.