/v2/* → version retirement
UptimeRobot API
Deprecated, no date
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.
Calls it hits
/v2/*
What to use instead of these calls
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.
In UptimeRobot API's words
You're viewing the legacy v2 API documentation. This version is no longer receiving updates or new features.
Facts
- API
- UptimeRobot API
api.uptimerobot.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against UptimeRobot API's own pages
Questions
When does this change take effect?
UptimeRobot API deprecated /v2/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: UptimeRobot 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.