GET /v1/reservations → endpoint removal
Hostaway API
Deprecated, no date
The query parameter offset on GET /v1/reservations has been deprecated without a shutdown date. Calls continuing to rely on this parameter will eventually fail once the deprecation is enforced. The provider announced this change on March 31, 2026, to encourage migration to afterId for better performance.
Calls it hits
GET /v1/reservationsquery parameter offset
What to use instead of these calls
Page through GET /v1/reservations using afterId with the last reservation ID of the previous page instead of offset.
In Hostaway API's words
Deprecated offset parameter in Retrieve a reservations list endpoint. Please migrate to afterId for better performance.
Facts
- API
- Hostaway API
api.hostaway.com - Kind
- Endpoint removal
- Announced
- March 31, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Hostaway API's own pages
Questions
When does this change take effect?
Hostaway API deprecated GET /v1/reservations, query parameter offset without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Hostaway 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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.