Ahrefs API
offset query parameter removal on /v3/*
Deprecated, no dateSubscribe to Ahrefs APIShare
The query parameter offset has been deprecated and removed from all /v3/* endpoints without a shutdown date. Calls passing offset fail, as the parameter has been deprecated and removed across the API.
Calls it hits
/v3/*query parameter offset
What to use instead of these calls
Stop sending offset, and narrow results with limit, order_by and where filters instead.
In Ahrefs API's words
The offset parameter has been deprecated and removed from all API endpoints.
Facts
- API
- Ahrefs API
api.ahrefs.com - Kind
- Parameter removal
- Announced
- May 31, 2024
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Ahrefs API's own pages
Questions
When does this change take effect?
Ahrefs API deprecated /v3/*, query parameter offset without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Ahrefs API has not given a shutdown date yet.
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 Ahrefs API 5
-
No date
GET /v3/site-explorer/domain-ratingParameter removal Deprecated, no date -
No date
GET /v3/keywords-explorer/matching-termsParameter removal Deprecated, no date -
No date
GET /v3/keywords-explorer/overviewParameter removal Deprecated, no date -
No date
GET /v3/keywords-explorer/search-suggestionsParameter removal Deprecated, no date -
No date
GET /v3/keywords-explorer/volume-by-countryParameter removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.