Checkly API
GET /swagger.json endpoint removal
Deprecated, no dateSubscribe to Checkly APIShare
Checkly has deprecated the GET /swagger.json endpoint without providing a shutdown date. Checkly API noted that this old API specification is frozen, and requests to it will eventually fail. This change directly affects any integrations fetching api.checklyhq.com/swagger.json.
Calls it hits
GET /swagger.json
What to use instead of these calls
Fetch the API contract from api.checklyhq.com/openapi.json instead to use the newer OpenAPI 3 specification.
In Checkly API's words
The old API spec at api.checklyhq.com/swagger.json is deprecated and frozen. Use the newer OpenAPI spec at api.checklyhq.com/openapi.json instead.
Facts
- API
- Checkly API
api.checklyhq.com - Kind
- Endpoint removal
- Announced
- May 18, 2026
- 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 /swagger.json 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 /v1/usage/seriesEndpoint 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.