MagicBell API
v1 /notifications API removal
Deprecated, no dateSubscribe to MagicBell APIShare
MagicBell deprecated the v1 notifications endpoints without a shutdown date. Calls matching notifications fail. MagicBell API notes that API v1 is deprecated.
Calls it hits
/notifications*
What to use instead of these calls
Read and mark notifications using the v2 endpoints under v2 notifications, including read, seen, archive, and unread count.
In MagicBell API's words
If you haven't migrated yet, the API v1 (deprecated) reference is here.
Facts
- API
- MagicBell API
api.magicbell.com - Kind
- Removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against MagicBell API's own pages
Questions
When does this change take effect?
MagicBell API deprecated /notifications* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: MagicBell 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 MagicBell API 2
-
No date
/broadcasts*Removal Deprecated, no date -
No date
/users*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.