Cloudflare API 403 Forbidden responses now include a documentation_url field that links directly to the API documentation for the endpoint that was denied. This gives developers, administrators, and agents an immediate path to the relevant docs with role information instead of guessing at which role or permission they are missing for that endpoint.
What’s New
Enriched 403 error responses: When a Cloudflare API request is denied, the error response now includes a documentation_url field that points to the documentation for that specific endpoint. Contextual 403 responses are now available across nearly all Cloudflare product APIs.
Faster troubleshooting: The linked API docs surface the roles required for each endpoint, making it easier to self-serve access issues.
Better support for tools and agents: Agents can use the \documentation_url` field to immediately fetch the endpoint’s documentation from the 403 error response, identify the accepted permissions for the denied action, and use that context to drive third-party approval workflows.`
Example 403 response:
{
"success": false,
"errors": [
{
"code": 10000,
"message": "Forbidden",
"documentation_url": "https://developers.cloudflare.com/api/resources/workers/subresources/beta/subresources/workers/methods/list"
}
],
"messages": [],
"result": null
}For more info:
Source: Cloudflare
