Miro REST API
/v1/users* version retirement
Deprecated, no dateSubscribe to Miro REST APIShare
Miro deprecated the /v1/users* endpoints without providing a shutdown date. Following the end-of-life for Miro v1 Developer Platform, calls to these endpoints will fail. The documentation for this version has been removed from the portal and is no longer maintained.
Calls it hits
/v1/users*
What to use instead of these calls
Move to the REST API v2 endpoints. Consult the REST API comparison guide at developers.miro.com/docs/rest-api-comparison-guide to map each v1 endpoint to its v2 equivalent.
In Miro REST API's words
Following the end-of-life for Miro v1 Developer Platform, its documentation has been removed from the portal and is no longer maintained.
Facts
- API
- Miro REST API
api.miro.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Miro REST API's own pages
Questions
When does this change take effect?
Miro REST API deprecated /v1/users* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Miro REST 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 Miro REST API 2
-
No date
/v1/boards*Version retirement Deprecated, no date -
No date
/v1/teams*Version retirement 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.