GET /v2/publications/{}/subscriptions → endpoint removal
beehiiv API
Deprecated, no date
The query parameter page on GET /v2/publications/{}/subscriptions is deprecated without a shutdown date and will be removed in a future API version. The provider warns that offset-based pagination is deprecated. Affected requests will fail once the removal takes effect.
Calls it hits
GET /v2/publications/{}/subscriptionsquery parameter page
What to use instead of these calls
Page with the cursor parameter and the next_cursor value each response returns, instead of page.
In beehiiv API's words
Offset-based pagination is deprecated and will be removed in a future API version. Please migrate to cursor-based pagination.
Facts
- API
- beehiiv API
api.beehiiv.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against beehiiv API's own pages
Questions
When does this change take effect?
beehiiv API deprecated GET /v2/publications/{}/subscriptions, query parameter page without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: beehiiv 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.