Last Call

AI on duty

Get the digest

API

Cloudflare

Cloudflare deprecates three Radar API endpoints — GET /radar/http/top/browser, GET /radar/http/top/browser_family, and GET /radar/netflows/summary — on 2 October 2026, with end of life on 2 April 2027; callers move to the dimensioned summary endpoints.

Boarding
150days00hrs00min

departs 2 Apr 2027

Official source Cloudflare API deprecations — Cloudflare Developers ↗ (developers.cloudflare.com)

Quick answers

Is it true that Cloudflare deprecates the Radar top-browsers and dimensionless NetFlows summary API endpoints — end of life 2 April 2027?
Yes. Cloudflare has officially announced it, effective 2 Apr 2027. If your code calls the Cloudflare Radar HTTP top-browsers endpoints or the dimensionless NetFlows summary endpoint, those routes are deprecated as of 2 October 2026 and stop working at end of life on 2 April 2027.
When does it take effect?
2 Apr 2027. Verified against the vendor's own announcement.
What should I use instead?
Repoint each deprecated call to its dimensioned replacement.

What this means for you

If your code calls the Cloudflare Radar HTTP top-browsers endpoints or the dimensionless NetFlows summary endpoint, those routes are deprecated as of 2 October 2026 and stop working at end of life on 2 April 2027. Three endpoints are affected: `GET /radar/http/top/browser`, `GET /radar/http/top/browser_family`, and `GET /radar/netflows/summary` (the variant with no dimension). Cloudflare is consolidating them into the newer dimensioned summary endpoints, so this is a path/shape change rather than a feature removal — the data remains available, but the request URL and the way you select a breakdown change. Anything that embeds these Radar routes — dashboards, internet-trends reports, research scripts, status pages that pull Cloudflare Radar data — needs its request paths updated before the 2027 cutoff.

Where to go

Repoint each deprecated call to its dimensioned replacement. `GET /radar/http/top/browser` and `GET /radar/http/top/browser_family` are both replaced by **`GET /radar/http/summary/{dimension}`**, passing the `BROWSER` or `BROWSER_FAMILY` dimension respectively. `GET /radar/netflows/summary` (dimensionless) is replaced by **`GET /radar/netflows/summary/{dimension}`** with the `PRODUCT` dimension. Update the request URLs and adjust any response parsing to the dimensioned summary shape, then re-test against live Radar data. You have until 2 April 2027, but the deprecated endpoints may return deprecation signalling before then, so migrate early rather than waiting for the hard cutoff.

  • GET /radar/http/summary/{dimension} with the BROWSER or BROWSER_FAMILY dimension — replaces the top-browsers endpoints
  • GET /radar/netflows/summary/{dimension} with the PRODUCT dimension — replaces the dimensionless NetFlows summary

Cloudflare has deprecated three Radar API endpoints, effective 2 October 2026, with end of life on 2 April 2027. Per Cloudflare’s API deprecations reference, the Radar top-browsers endpoints and the dimensionless NetFlows summary endpoint are being folded into newer summary endpoints that take a {dimension} path parameter.

What is deprecated

  • GET /radar/http/top/browser
  • GET /radar/http/top/browser_family
  • GET /radar/netflows/summary (the variant with no dimension)

These are part of Cloudflare Radar, the public internet-trends service, so the callers most affected are dashboards, research and reporting scripts, and status pages that pull Radar data — not production traffic-serving code.

The replacements

This is a consolidation, not a removal — the same data is reachable through dimensioned endpoints:

  • GET /radar/http/top/browser → GET /radar/http/summary/{dimension} with the BROWSER dimension.
  • GET /radar/http/top/browser_family → GET /radar/http/summary/{dimension} with the BROWSER_FAMILY dimension.
  • GET /radar/netflows/summary → GET /radar/netflows/summary/{dimension} with the PRODUCT dimension.

What to do

Update the request URLs in any code that hits the three deprecated routes, switch to selecting the breakdown via the {dimension} path parameter, and adjust response parsing to the dimensioned summary shape. The deprecated endpoints keep working until 2 April 2027, but migrate early — deprecated Cloudflare endpoints typically start returning deprecation signalling ahead of the hard cutoff. The lastcall CLI fingerprints the two top-browser paths so it can flag them if they’re still hard-coded in your repo.

Entry changelog

  • — last reviewed.
  • — Entry created from Cloudflare's official API deprecations reference. The deprecation date (2 October 2026), end-of-life date (2 April 2027), the three deprecated endpoints (GET /radar/http/top/browser, GET /radar/http/top/browser_family, GET /radar/netflows/summary), and their dimensioned replacements (GET /radar/http/summary/{dimension}; GET /radar/netflows/summary/{dimension}) are quoted directly from Cloudflare's page; no inference. detect: fingerprints are the two concrete top-browser request paths — literal strings REST/HTTP client code contains. The dimensionless NetFlows path is deliberately NOT fingerprinted because its replacement, /radar/netflows/summary/{dimension}, contains the same prefix and would produce false positives on migrated code.

Related on the calendar

Put this countdown in your README

Building on Cloudflare? Drop this badge into a project’s README or docs — it shows the days left and refreshes on its own every night from this page. Last Call countdown for Cloudflare deprecates three Radar API endpoints — GET /radar/http/top/browser, GET /radar/http/top/browser_family, and GET /radar/netflows/summary — on 2 October 2026, with end of life on 2 April 2027; callers move to the dimensioned summary endpoints. 

[![Last Call countdown](https://lastcall.dev/badge/cloudflare-radar-top-browsers-netflows-summary-eol.svg)](https://lastcall.dev/entries/cloudflare-radar-top-browsers-netflows-summary-eol)

Spot an error or a changed date? Tell us and it’s corrected the same night.