/api/v2/* → version retirement
Deprecated, no date
The provider has deprecated the REST API v2 without a shutdown date, urging users to migrate as soon as possible. This deprecation affects all /api/v2/* calls. Once retired, requests sent to these endpoints will fail.
Calls it hits
/api/v2/*
What to use instead of these calls
Update endpoints by changing /api/v2/ to /api/v3/ in your URL paths. The move requires more than an identifier change, as markdown text processing differs between versions.
In Shortcut API's words
This version (v2) of the API is deprecated. Please migrate to v3 as soon as possible.
Facts
- API
- Shortcut API
api.app.shortcut.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Shortcut API's own pages
Questions
When does this change take effect?
Shortcut API deprecated /api/v2/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Shortcut 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.