Connect Cloudflare to Saasmetry

Request volume, cache hit ratio, p95 latency and blocked threats per zone.

What Saasmetry reads

Refreshed every 10 min. Read-only throughout: Saasmetry never writes to Cloudflare.

My Profile → API Tokens → Create Token → Custom token. Account-owned tokens under Manage Account → Account API Tokens work equally well.
Set a permission row's first dropdown to Zone, then choose Analytics → Read. Add a second row for Zone → Zone → Read.
Under Resources, include All zones from an account — or name the zones individually.

Account → Analytics Read is a different permission and covers none of this. A token with every account permission ticked is still refused.
The Resources selector is the half most people miss: zone analytics cannot be granted by a policy whose resources contain no zones.
Listing zones and reading their analytics are separate permissions, so Saasmetry runs one analytics query at connect time — a token that can only list zones is rejected there rather than reporting nothing for a week.

Use read-only scopes wherever the provider offers them. Saasmetry encrypts the credential and only reads provider data.

Free plan, no card: one product and two integrations.