Normalize SIRENE, Companies House and VIES into a single JSON schema. No auth juggling, no field mapping, no maintenance.
Powered by official registries
SIRENE
INSEE · France
Companies House
HMRC · United Kingdom
VIES
European Commission · 27 countries
27
Countries covered (VAT)
< 200ms
Cached response time
24h
Data freshness
Request
curl 'https://eubase.dev/api/v1/company/search?name=doctolib&country=FR' \ -H 'X-API-Key: eb_live_...'
Response
{
"results": [
{
"id": "FR_794598813",
"name": "Doctolib",
"confidence": 0.98,
"status": "active",
"vat_number": "FR14794598813",
"incorporation_date": "2013-07-15",
"legal_form": "Société par actions simplifiée",
"address": {
"street": "54 QUAI CHARLES PASQUA",
"city": "LEVALLOIS-PERRET",
"postal_code": "92300"
},
"industry": { "code": "62.01Z", "label": "Programmation informatique" },
"officers": [{ "name": "Stanislas Niox-Chateau", "role": "Président" }],
"sources": ["SIRENE"]
}
],
"meta": { "query": "doctolib", "country": "FR", "total": 1 }
}You can. Here's what that looks like in practice.
Three incompatible schemas
SIRENE returns siren + siege, Companies House returns company_number + registered_office_address. You write the mapping layer. Then you maintain it.
No unified auth model
INSEE needs no key. Companies House needs Basic Auth. VIES is SOAP. Each integration is a different protocol.
Upstream changes break you
Registries update their schemas without notice. Every field rename is your bug to chase. eubase absorbs the change — your code stays the same.
Start free. Upgrade when you need more.