Gandi API
offset query parameter removal on GET /v5/linkedzone/*
Stopped workingSubscribe to Gandi APIShare
On January 5, 2026, the query parameter offset was removed from GET /v5/linkedzone/* endpoints. Calls using this parameter fail after that day. This breaking change applies across linked zone endpoints such as GET /v5/linkedzone/domains, GET /v5/linkedzone/tasks, and GET /v5/linkedzone/zones.
Calls it hits
GET /v5/linkedzone/*query parameter offset
What to use instead of these calls
Paginate with page and per_page instead of offset and limit.
In Gandi API's words
Replace the limit and offset parameters by the per_page and page parameters to paginate the responses: GET /v5/linkedzone/domains , GET /v5/linkedzone/tasks , GET /v5/linkedzone/zones .
Facts
- API
- Gandi API
api.gandi.net - Kind
- Parameter removal
- Announced
- January 5, 2026
- Takes effect
- January 5, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Gandi API's own pages
Questions
When does this change take effect?
Calls to GET /v5/linkedzone/*, query parameter offset on Gandi API stopped working on January 5, 2026.
What happens to calls after January 5, 2026?
They have failed since January 5, 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 Gandi API 3
-
GET /v5/linkedzone/*Parameter removal Stopped working -
No date
/v5/email/*Removal Deprecated, no date -
No date
/v5/simplehosting/*Parameter removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.