GET /radar/attacks/layer3/top/industry → endpoint removal
Cloudflare API
Stopped working
On September 20, 2025, Cloudflare API will remove the endpoint GET /radar/attacks/layer3/top/industry. Requests made to this endpoint after that day will fail.
Calls it hits
GET /radar/attacks/layer3/top/industry
What to use instead of these calls
Update requests to use GET /radar/attacks/layer3/summary/industry instead.
In Cloudflare API's words
GET /radar/attacks/layer3/top/industry
Facts
- API
- Cloudflare API
api.cloudflare.com - Kind
- Endpoint removal
- Announced
- March 20, 2025
- Takes effect
- September 20, 2025
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Cloudflare API's own pages
Questions
When does this change take effect?
Calls to GET /radar/attacks/layer3/top/industry on Cloudflare API stopped working on September 20, 2025.
What happens to calls after September 20, 2025?
They have failed since September 20, 2025.
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 Cloudflare API 6
-
GET /zones/:zone_id/settings/cname_flatteningEndpoint removal Stopped working -
GET /zones/:zone_id/firewall/waf/packages/:package_id/rules/:rule_idEndpoint removal Stopped working -
GET /radar/attacks/layer3/top/verticalEndpoint removal Stopped working -
GET /radar/attacks/layer7/top/industryEndpoint removal Stopped working -
GET /radar/attacks/layer7/top/verticalEndpoint removal Stopped working -
GET /zones/{}/amp/sxgEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.