Checkly API
GET /v1/usage/series endpoint removal
Deprecated, no dateSubscribe to Checkly APIShare
Checkly API has deprecated the GET /v1/usage/series endpoint without setting a shutdown date. Calls made to this route will eventually fail. The change applies to all callers using this path.
Calls it hits
GET /v1/usage/series
What to use instead of these calls
Read usage over time with GET /v2/usage/series instead.
In Checkly API's words
Deprecated. Use GET /v2/usage/series for usage across terms and pricing rules.
Facts
- API
- Checkly API
api.checklyhq.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Checkly API's own pages
Questions
When does this change take effect?
Checkly API deprecated GET /v1/usage/series without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Checkly 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.
More from Checkly API 3
-
No date
GET /swagger.jsonEndpoint removal Deprecated, no date -
No date
GET /v1/usage/summaryEndpoint removal Deprecated, no date -
No date
GET /v1/usage/termsEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.