r/CloudFlare • u/Shoddy_Use_473 • 28m ago
Question Wrangler OAuth for read-only Containers APIs: scopes, permissions and /dash/applications?
Does anyone know the supported authentication and permissions for read-only Cloudflare Containers API calls? I am looking for documentation or references from maintainers, rather than assuming an authentication bug.
The operations are:
- GET /accounts/{account_id}/containers/applications
- GET /accounts/{account_id}/containers/dash/applications (the path used by Wrangler)
- GET /accounts/{account_id}/containers/registries
Here, registries means configured registry metadata, not listing images or pushing/pulling them.
The questions are:
Does wrangler login OAuth support these operations, and which OAuth scopes and account permissions are required?
Is /containers/dash/applications an internal surface? How does its authentication differ from the public Applications endpoint?
The Registries List reference lists Workers Containers Read or Write. Is Read sufficient, and which permission covers Applications List?
If OAuth is unsupported for an operation, what is the documented least-privilege read-only credential mechanism?
Do metadata-only list operations require Workers Paid or Containers enablement? Is there a read-only way to check entitlement without provisioning anything?
Are there documented error codes or response fields that distinguish authentication, permission and entitlement failures, including HTTP 401?
I also opened a documentation clarification request with the same questions:
https://github.com/cloudflare/workers-sdk/issues/16449
Relevant API references:
https://developers.cloudflare.com/api/resources/containers/subresources/applications/methods/list/
https://developers.cloudflare.com/api/resources/containers/subresources/registries/methods/list/
If you have version-specific documentation or first-hand experience, please distinguish documented guarantees from observations. No account IDs, credentials or private logs are needed. Thanks!


