BODACC API : authentication and limits
Free public access
The BODACC API is open without a key on all data endpoints: notices, companies, people, directory, statistics. You can query public data immediately:
curl "https://bodacc.io/api/bodacc/annonces?q=boulangerie&limit=5"
Get an API key
Pro and Enterprise plans provide API keys (prefix sk_bodacc_) from your My account → API area (/{locale}/mon-compte/api). The key unlocks the documented endpoints that require it.
Pass the key
Two accepted headers:
# X-API-Key header
curl "https://bodacc.io/api/bodacc/annonces?q=boulangerie" \
-H "X-API-Key: sk_bodacc_..."
# Or Authorization Bearer
curl "https://bodacc.io/api/bodacc/annonces?q=boulangerie" \
-H "Authorization: Bearer sk_bodacc_..."
An invalid or revoked key returns 401 with an explicit JSON body. A missing key leaves public access open (no error).
Error codes
| Code | Meaning |
|---|---|
400 | Invalid parameter (e.g. unknown directory role) |
401 | Invalid or revoked API key |
404 | Resource not found (notice, SIREN, person) |
429 | Too many requests — respect Retry-After |
Limits and best practices
- Anti-dump bounds:
limit≤ 500,offset≤ 10 000 on notices/companies/firms; directory bounded to 200 pages of 100 - Systematic pagination: iterate over
offset(orpage/per_pagefor the directory) instead of requesting large volumes Retry-After: on429, wait the indicated duration before retrying- Totals: prefer
stats/countsandstats/daily(materialized) overCOUNT(*)for dashboards - Real-time data: data is refreshed after each BODACC publication
Go further
- Quickstart: first call
- Search notices: search parameters
- Statistics: counters and series