History of SIRET Code Changes

Open data API in a single place

Provided by Christian Quest

Get early access to History of SIRET Code Changes API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Christian Quest catalog

Country of origin

France

Updated

2018.03.07 12:17

Created

2018.02.28

Available languages

English

Keywords

entreprises, sirene, siret

Datasource

Official portal for European data link

Quality scoring

Dataset description

This dataset is automatically extracted from the daily data of the [INSEE SIRENE database](https://www.data.gouv.fr/fr/datasets/base-sirene-des-entreprises-et-de-leurs-etablissements-siren-siret/). It provides a list of establishment code changes (SIRET) following, for example, a change of address or business transfer between companies. It is updated daily from INSEE’s daily update files. The CSV files produced contain: — the old SIRET code — the new SIRET code — the date of change Processing scripts are available at https://github.com/cquest/histo_sirene Improvements and remarks are welcome! Added 2/3/2018: changes to SIRET are no longer limited to identical SIRENs.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service