Updatesapi-cloudflare

Cloudflare API: 9 Breaking Changes in Instances, Completions

5a18cffd013f → 6aa086d6d5faVerified February 19, 2026

TL;DR

  • The source_params property in responses is now nullable for the 200 and 201 statuses.
  • Request property patterns for source_params/exclude_items/items/ and source_params/include_items/items/ have been updated.
  • New optional properties result/items/fusion_method and result/fusion_method have been added to responses.
  • The fusion_method request property has been introduced as an optional parameter.
  • The default value of map[r2_jurisdiction:default] for source_params has been removed in responses.

    • Editor's Note:

    As we review this update, we notice it's part of a series of changes aimed at enhancing the flexibility and customization of AI search instances. This shift towards more nuanced control over search parameters and results reflects recent trends in developer demand for more sophisticated search functionalities. One practical tip for developers affected by these changes is to review their current implementations and adjust their handling of source_params and fusion_method to take advantage of the new optional properties and parameters.

    What Changed

    #### Breaking

  • The response property result/items/source_params became nullable for the 200 status in the /accounts/{account_id}/ai-search/instances endpoint.
  • The response property result/source_params became nullable for the 201 status in the /accounts/{account_id}/ai-search/instances endpoint.
  • The response property result/source_params became nullable for the 200 status in the /accounts/{account_id}/ai-search/instances/{id} endpoint.
  • The pattern of the request property source_params/exclude_items/items/ was changed from ^[/\\\\]?[\\w\\-\\/.\\\\?:=&%]+$ to ^[/\\\\]?[\\w\\-/.\\\\?:=&%]+$.
  • The pattern of the request property source_params/include_items/items/ was changed from ^[/\\\\]?[\\w\\-\\/.\\\\?:=&%]+$ to ^[/\\\\]?[\\w\\-/.\\\\?:=&%]+$.

    • #### Deprecation

    No deprecations were found in this update.

    #### Behavior

  • The source_params response property's default value map[r2_jurisdiction:default] was removed for the 200 status.
  • The result/items/source_params/exclude_items/items/ response property's pattern was changed from ^[/\\\\]?[\\w\\-\\/.\\\\?:=&%]+$ to ^[/\\\\]?[\\w\\-/.\\\\?:=&%]+$ for the 200 status.
  • The result/items/source_params/include_items/items/ response property's pattern was changed from ^[/\\\\]?[\\w\\-\\/.\\\\?:=&%]+$ to ^[/\\\\]?[\\w\\-/.\\\\?:=&%]+$ for the 200 status.
  • The request property source_params became nullable.
  • The source_params request property's default value map[r2_jurisdiction:default] was removed.

    • #### Feature

  • The optional property result/items/fusion_method was added to the response with the 200 status.
  • The optional property result/fusion_method was added to the response with the 201 status.
  • The new optional request property fusion_method was introduced.

    • Who's Impacted

    If you are currently using the source_params property in your requests or responses, you will need to adjust your implementation to handle the new nullable behavior. If you are relying on the default value of map[r2_jurisdiction:default] for source_params, you will need to provide this value explicitly or handle the case where it is not present. If you are interested in utilizing the new fusion_method property for more customized search results, you should review the updated API documentation to understand how to integrate this feature into your application.

    Action Checklist

  • ☐ Review current implementations for handling of source_params.
  • ☐ Update code to handle nullable source_params in responses.
  • ☐ Adjust request patterns for source_params/exclude_items/items/ and source_params/include_items/items/.
  • ☐ Test for removal of default source_params value.
  • ☐ Integrate new fusion_method request property where applicable.
  • ☐ Update documentation to reflect changes in API behavior.
  • ☐ Verify compatibility with existing search functionalities.
  • ☐ Adjust error handling for potential issues with new property patterns.
  • ☐ Review API documentation for correct usage of new optional properties.
  • ☐ Plan for potential future deprecations based on current changes.
  • ☐ Communicate changes to team members who may be affected.
  • ☐ Schedule testing for updated API endpoints.
  • ☐ Monitor API performance after updating to the new version.
  • ☐ Review security implications of new properties and patterns.

    • Verification

    This update brief is based on information from the following sources:

  • Commit 6aa086d6d5fa: https://github.com/cloudflare/api-schemas/commit/6aa086d6d5fa1034c29d6049c34913c20a790d2e
  • Cloudflare API Spec Diff: https://github.com/cloudflare/api-schemas/compare/5a18cffd013f799a9781e31a3f90d2ee6183684f...6aa086d6d5fa1034c29d6049c34913c20a790d2e

    • Last verified at 2026-02-19T14:40:51.716589+00:00.

    📎 Sources