![]()
api.fastly.com · CloudSubscribeShare
Fastly API breaking changes
The breaking changes Fastly API announced that Okapi tracks: 3 in all.
Do you run the Fastly API? Make sure your users call it right →
At a glance
- API host
api.fastly.com- Kind
- Cloud
- Versions with breaking changes
- v2 (1)
- Breaking changes tracked
- 1 breaking change with no date yet and 2 already in effect
- Last updated
Deprecated, no date yet 1
-
No date
POST /userEndpoint removal Deprecated, no date
Already in effect 2
-
/security/*Endpoint removal Stopped working -
/billing/v2/*Version retirement Stopped working
Where Okapi reads it
- Changelog www.fastly.com/documentation/reference/changes/api/
- Announcement www.fastly.com/documentation/reference/changes/2025/03/remove-billing-v2-endpoints
- Announcement www.fastly.com/documentation/reference/changes/2025/04/migrate-routes-from-security-to-ngwaf-v1
- Announcement www.fastly.com/documentation/reference/changes/2025/04/user-create-deprecation
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub