/v1/* → version retirement
Vultr API
Stopped working
On October 2, 2023, the v1 API was taken offline and is no longer usable. This retirement affects all /v1/* endpoints. Requests sent to these endpoints now fail.
Calls it hits
/v1/*
What to use instead of these calls
Migrate by calling the v2 API instead. This transition requires sending your API key as a bearer token in the Authorization header and updating resource identifiers from numeric IDs to UUIDs.
In Vultr API's words
API v1: Deprecated and taken offline; no longer usable. Use API v2 instead
Facts
- API
- Vultr API
api.vultr.com - Kind
- Version retirement
- Takes effect
- October 2, 2023
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Vultr API's own pages
Questions
When does this change take effect?
Calls to /v1/* on Vultr API stopped working on October 2, 2023.
What happens to calls after October 2, 2023?
They have failed since October 2, 2023.
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.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.