Miro REST API
/v1/teams* version retirement
Deprecated, no dateSubscribe to Miro REST APIShare
The /v1/teams* endpoints have reached end-of-life as part of the Miro v1 Developer Platform retirement. Miro deprecated these endpoints without a shutdown date, and documentation for them has been removed. Calls targeting /v1/teams* now fail.
Calls it hits
/v1/teams*
What to use instead of these calls
Move to the REST API v2 endpoint /v2/orgs/{org_id}/teams. Consult the Miro REST API comparison guide for mappings from v1 endpoints to v2 equivalents.
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/teams* 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/users*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.