Okapi Okapi

MagicBell API v1 /users API removal

Deprecated, no dateSubscribe to MagicBell APIShare

MagicBell deprecated the v1 /users endpoints without a shutdown date. Calls matching /users* will eventually fail as MagicBell API phases out the older interface. The documentation notes that v1 is deprecated for projects that have not yet migrated.


Calls it hits

  • /users*

What to use instead of these calls

Manage users using GET and PUT requests to the v2 users endpoint, and DELETE requests to /v2/users/{user_id}.

In MagicBell API's words

If you haven't migrated yet, the API v1 (deprecated) reference is here.

MagicBell API, Announcement

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 /users* 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

  1. No date /broadcasts*Removal Deprecated, no date
  2. No date /notifications*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.

Add to GitHub

Get notifications

Subscribe to MagicBell API

Hear about each breaking change MagicBell API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • MagicBell API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.