data.gouv.fr API
/api/1/me/apikey endpoint removal
Stopped workingSubscribe to data.gouv.fr APIShare
Calls to /api/1/me/apikey on data.gouv.fr API stopped working on March 24, 2026.
Calls it hits
/api/1/me/apikey
What to use instead of these calls
Manage tokens by using POST /api/1/me/api_tokens/ to create them, GET /api/1/me/api_tokens/ to list them, and DELETE /api/1/me/api_tokens/{id}/ to revoke them.
In data.gouv.fr API's words
Remove the apikey field from the User model and the me_fields / apikey_fields API serializers, along with the old /me/apikey/ endpoint
Facts
- API
- data.gouv.fr API
www.data.gouv.fr - Kind
- Endpoint removal
- Takes effect
- March 24, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against data.gouv.fr API's own pages
Questions
When does this change take effect?
Calls to /api/1/me/apikey on data.gouv.fr API stopped working on March 24, 2026.
What happens to calls after March 24, 2026?
They have failed since March 24, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from data.gouv.fr API 2
-
GET /api/1/territory/suggestEndpoint removal Stopped working -
/api/1/harvest/job_statusRemoval Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.