# The v2 API is deprecated

UptimeRobot API deprecated /v2/* without giving a shutdown date yet.

The provider has deprecated the legacy v2 API without a shutdown date. This deprecation affects all /v2/* endpoints, which no longer receive updates or new features. Requests to these endpoints will eventually fail.

## What to use instead

Migrate to the v3 API at api.uptimerobot.com/v3. The move requires more than changing an identifier, as v3 uses resource paths with standard HTTP verbs such as GET /v3/monitors and PATCH /v3/monitors/{id}, cursor pagination, and API keys passed as bearer tokens.

- API: UptimeRobot API (api.uptimerobot.com)
- Kind: Version retirement
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `/v2/*`
- Source: [Announcement](https://uptimerobot.com/api/legacy/)
- Verified: October 26, 2026, against UptimeRobot API's own pages
- Page: https://www.okapi.bot/providers/uptimerobot-api/breaking-changes/the-v2-api-is-deprecated/

## UptimeRobot API's words

> You're viewing the legacy v2 API documentation. This version is no longer receiving updates or new features.

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