orias.fr APIorias.fr ↗
Search and retrieve profiles of French insurance, banking, and finance intermediaries from the official ORIAS registry. Registration status, mandates, and services.
curl -X GET 'https://api.parse.bot/scraper/37a14ba1-e2dd-4b3f-8766-be367f29c78f/search_intermediaries?page=1&step=INTERMEDIAIRE&query=PETIT' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for intermediaries in the ORIAS registry using wildcards or keywords. Returns paginated results with 20 items per page. Requires two HTTP requests internally (homepage for session token, then search POST).
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| step | string | Type of intermediaries: 'INTERMEDIAIRE' (standard) or 'ENTRANTE' (European/Notifications). |
| query | string | Wildcard character '%' or search keyword (SIREN, Orias number, Name). |
{
"type": "object",
"fields": {
"page": "integer current page number",
"step": "string the step type used in the search",
"items": "array of intermediary summary objects with orias_number, status, siren, name, categories, postal_code, city, country, id",
"total_results": "integer total number of matching intermediaries"
},
"sample": {
"data": {
"page": 1,
"step": "INTERMEDIAIRE",
"items": [
{
"id": "453348948",
"city": "ANNEVILLE SUR SCIE",
"name": "Fabrice PETIT",
"siren": "453348948",
"status": "INSCRIT",
"country": "France",
"categories": [
{
"name": "COA",
"status": "ACTIF"
},
{
"name": "COBSP",
"status": "ACTIF"
}
],
"postal_code": "76590",
"orias_number": "07004126"
}
],
"total_results": 288
},
"status": "success"
}
}About the orias.fr API
The ORIAS API covers France's official registry of financial intermediaries across 2 endpoints, returning over 10 fields per intermediary including registration status, SIREN number, activity categories, and mandate details. Use search_intermediaries to query by name, SIREN, or ORIAS number with wildcard support, and get_intermediary_details to pull a full compliance profile for any registered entity.
Search the ORIAS Registry
The search_intermediaries endpoint queries the French ORIAS directory and returns paginated results of 20 items per page. The query parameter accepts a SIREN number, an ORIAS registration number, a company name, or the wildcard character % to browse broadly. The step parameter filters between INTERMEDIAIRE (standard French intermediaries) and ENTRANTE (European passport notifications). Each result object includes orias_number, siren, name, status, categories, postal_code, city, country, and an id field used for follow-up lookups.
Retrieve Full Intermediary Profiles
The get_intermediary_details endpoint accepts the id (SIREN) from search results and returns two top-level objects. The details object covers the intermediary's basic identity: commercial trade name (sigle_enseigne_nom_commercial), legal form (forme_ju), ORIAS number, SIREN, current status (statut), and registration state (etat_and_inscriptions). The registrations array lists every regulatory category the intermediary holds, with activity_type, type_code, type_full, status, status_date, financial_rights, and where applicable, associated mandates and service authorizations.
Coverage and Data Scope
ORIAS (Organisme pour le Registre des Intermédiaires en Assurance) is the sole official French register mandated by law for insurance brokers (IAS), banking intermediaries (IOBSP), investment advisers (CIF), and crowdfunding intermediaries (IFP/PSI). Data returned by this API reflects those official registry records, making it suitable for KYC workflows, compliance checks, and partner vetting in regulated French financial contexts.
- Verify that a French insurance broker is currently registered before onboarding them as a partner, using their ORIAS number and
statusfield. - Look up all intermediaries in a specific city or region by combining a name wildcard query with
postal_codefrom search results. - Check which regulatory categories (
activity_type,type_code) an intermediary is authorized for before accepting a mandate. - Cross-reference a company's SIREN from a CRM against ORIAS registration data to flag unregistered entities in a compliance pipeline.
- Monitor changes in an intermediary's
statusorstatus_dateacross registrations to detect lapses or renewals. - Enumerate European passport intermediaries (
step=ENTRANTE) operating in France to assess market exposure. - Identify the full set of services and mandates held by a counterparty before executing a distribution agreement.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does ORIAS provide an official public developer API?+
What does `get_intermediary_details` return beyond basic contact info?+
registrations array covering every regulatory category held by the intermediary. Each registration object includes activity_type, type_code, type_full, status, status_date, and financial_rights, plus associated mandates and service authorizations where the intermediary has them on record.How does pagination work in `search_intermediaries`?+
total_results integer so you can calculate how many pages exist. Pass the page parameter to navigate through results. Note that very broad queries (such as the % wildcard) may return a large number of pages.Does the API return historical registration data or audit trails?+
status_date, but does not expose a full history of past registrations, category changes, or sanction records. You can fork this API on Parse and revise it to add an endpoint that tracks or stores historical snapshots of intermediary profiles.Can I search by activity type or filter results to a specific regulatory category?+
search_intermediaries endpoint filters by step (standard vs. European passport intermediaries) and by keyword or identifier via query, but does not currently accept a direct filter for activity type or regulatory category. Category data is available in the response categories field per result, and in full detail via get_intermediary_details. You can fork the API on Parse and revise it to add category-based filtering logic.