Updatesapi-cloudflare

Cloudflare API: 4 Breaking Changes in Policies

6aa086d6d5fa → 904f351e29feVerified February 19, 2026

TL;DR

  • The add_reporting_directives enum value has been added to the action response property for the 200 response status in the /zones/{zone_id}/page_shield/policies and /zones/{zone_id}/page_shield/policies/{policy_id} endpoints.
  • This change is considered breaking and requires immediate attention from developers using these endpoints.
  • The add_reporting_directives enum value has also been added to the action request property in both endpoints.
  • Developers should review their code to ensure compatibility with these changes.
  • The updated API spec can be found in the commit 904f351e29fe and the Cloudflare API Spec Diff.

    • What Changed

  • Breaking: Four breaking changes have been introduced, all related to the addition of the add_reporting_directives enum value to the action response property in the /zones/{zone_id}/page_shield/policies and /zones/{zone_id}/page_shield/policies/{policy_id} endpoints.
  • Feature: Two new features have been added, introducing the add_reporting_directives enum value to the action request property in both endpoints.

    • Editor's Note:

    We consider this update a significant shift in the Cloudflare API, as it introduces a new enum value that can impact how developers handle responses from the Page Shield policies endpoints. As we've seen in recent trends, Cloudflare has been focusing on enhancing their security features, and this update is a part of that effort. When reviewing your code, we recommend starting with the /zones/{zone_id}/page_shield/policies endpoint, as it is likely to be the most impacted by these changes.

    Who's Impacted

    If you are currently using the /zones/{zone_id}/page_shield/policies or /zones/{zone_id}/page_shield/policies/{policy_id} endpoints, you will need to update your code to handle the new add_reporting_directives enum value. If you are relying on the action response property in these endpoints, you should review your code to ensure compatibility with the breaking changes. If you are using the action request property in these endpoints, you can now utilize the new add_reporting_directives enum value to enhance your application's functionality.

    Action Checklist

  • ☐ Review the updated API spec in the commit 904f351e29fe to understand the changes.
  • ☐ Update your code to handle the new add_reporting_directives enum value in the action response property.
  • ☐ Test your application to ensure compatibility with the breaking changes.
  • ☐ Review the Cloudflare API Spec Diff to understand the changes.
  • ☐ Update your documentation to reflect the changes in the API.
  • ☐ Inform your team about the changes and their impact on your application.
  • ☐ Plan for potential errors that may arise from the changes.
  • ☐ Implement error handling for the new add_reporting_directives enum value.
  • ☐ Verify that your application is working as expected after the updates.
  • ☐ Monitor your application's performance after the updates.
  • ☐ Review the /zones/{zone_id}/page_shield/policies endpoint to ensure compatibility.
  • ☐ Review the /zones/{zone_id}/page_shield/policies/{policy_id} endpoint to ensure compatibility.
  • ☐ Update your request handling to utilize the new add_reporting_directives enum value.
  • ☐ Test your request handling to ensure compatibility with the new enum value.

    • Verification

    The information in this brief is based on the following sources:

  • Commit 904f351e29fe: https://github.com/cloudflare/api-schemas/commit/904f351e29fec95a7897de0c4a6450e24e696c6d
  • Cloudflare API Spec Diff: https://github.com/cloudflare/api-schemas/compare/6aa086d6d5fa1034c29d6049c34913c20a790d2e...904f351e29fec95a7897de0c4a6450e24e696c6d

    • Last verified at: 2026-02-19T20:41:55.634344+00:00

    📎 Sources