# The v1 API stops working

Calls to /v1/* on Vultr API stopped working on October 2, 2023.

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.

## What to use instead

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.

- API: Vultr API (api.vultr.com)
- Kind: Version retirement
- Takes effect: October 2, 2023
- Calls after that day: fail
- Calls it hits: `/v1/*`
- Source: [Announcement](https://docs.vultr.com/platform/api-opensource-changelog.md)
- Verified: October 26, 2026, against Vultr API's own pages
- Page: https://www.okapi.bot/providers/vultr-api/breaking-changes/the-v1-api-stops-working/

## Vultr API's words

> API v1: Deprecated and taken offline; no longer usable. Use API v2 instead

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent