Fastly API
/security/* endpoint removal
Stopped workingSubscribe to Fastly APIShare
On April 22, 2026, legacy /security/* endpoints were permanently removed from the Fastly API. Calls directed to these routes fail since that date.
Calls it hits
/security/*
What to use instead of these calls
Replace the /security base path with /ngwaf/v1, such as /ngwaf/v1/workspaces. Schemas and authentication remain unchanged.
In Fastly API's words
The new endpoints are available now, and legacy /security routes will remain operational until April 22, 2026, when they will be permanently removed.
Facts
- API
- Fastly API
api.fastly.com - Kind
- Endpoint removal
- Announced
- April 22, 2025
- Takes effect
- April 22, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Fastly API's own pages
Questions
When does this change take effect?
Calls to /security/* on Fastly API stopped working on April 22, 2026.
What happens to calls after April 22, 2026?
They have failed since April 22, 2026.
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 Fastly API 2
-
/billing/v2/*Version retirement Stopped working -
No date
POST /userEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.