Cloudflare Python SDK levels up to v5.0.0-beta.1 - packed with new resources, but watch for breaking changes

Hi, I'm Shii-chan! I found some interesting news around Cloudflare's SDK today, so let's dig in together. If you're using the Cloudflare API from Python, this one's worth a look.

Cloudflare Changelog developers.cloudflare.com

What was announced?

According to the Cloudflare Changelog, on February 13, 2026, a new version of the official Python SDK, cloudflare-python, shipped as v5.0.0-beta.1. The official note says "v5.0.0-beta.1 is in Beta and we are still testing it for stability," so this is a beta build, not a final release yet. The full list of changes since the previous stable release, v4.3.1, is published on GitHub's comparison page.

The story so far

cloudflare-python is auto-generated from Cloudflare's OpenAPI definitions. That means whenever the underlying OpenAPI schemas change, or the codegen tooling that reads those schemas is updated, the impact flows straight through to the SDK. The official announcement explains that most of this release's breaking changes come from improvements to the accuracy of the base OpenAPI schemas - changes made to get things more correct that, unfortunately, end up breaking existing client code. It looks like a backlog of schema inconsistencies got cleaned up all at once in this v5 line.

What changes

The most eye-catching part of this beta is the sheer number of new resources. Counting them up, I found 48 brand-new resources. Here are some of the areas that grew:

• aisearch family - AI-powered search, plus instance and token management
• aigateway.dynamicrouting / aigateway.providerconfigs - dynamic routing and provider configuration for AI Gateway
• brandprotection family - logo detection and match results for brand protection
• pipelines family - data pipeline management, including sinks and streams
• r2datacatalog family - namespaces and credentials for R2 Data Catalog
• realtimekit family - live streaming, meetings, recordings, and more
• tokenvalidation family - token validation configuration and rules
• workers.beta - beta Workers features

On top of that, 11 existing resources, including acm.totaltls, d1.database, radar.bgp, and zerotrust.networks, picked up new endpoints, so there is value here even for existing users. If you build on Cloudflare's services from Python, a lot of operations that were not possible through the SDK before are now on the table.

Dive Deep

The thing to watch most closely in this release is exactly what is in the title: breaking changes. The following 15 resources have breaking changes in this release:

• abusereports
• acm.totaltls
• apigateway.configurations
• cloudforceone.threatevents
• d1.database
• intel.indicatorfeeds
• logpush.edge
• origintlsclientauth.hostnames
• queues.consumers
• radar.bgp
• rulesets.rules
• schemavalidation.schemas
• snippets
• zerotrust.dlp
• zerotrust.networks

Cloudflare urges everyone to read the v5 Migration Guide and the full change list before upgrading, since it may cause upstream or downstream issues depending on your environment. They also note that some changes might not be captured in the changelog yet, and invite you to open a GitHub issue if you spot anything missing.

There is also a batch of smaller fixes worth knowing about:

• Type system: Pyright can now correctly infer TypedDict types inside SequenceNotStr, and compatibility with Pydantic versions before 2.8.0 has been restored
• Request/response handling: fixed sending multipart/form-data together with JSON, headers whose default value is omit are no longer sent, and GET requests no longer send an unnecessary Content-Type header
• Parsing: fixed handling of nested discriminated unions, corrected parsing of extra field types, empty metadata fields are now ignored, and the resource-name singularization rules were updated

Wrap-up

• Cloudflare's official Python SDK shipped as a beta, v5.0.0-beta.1
• 48 new resources plus new endpoints on 11 existing resources significantly widen what the SDK can do
• 15 resources carry breaking changes, so checking the migration guide before upgrading is a must
• The release also includes plenty of under-the-hood fixes to type inference and request handling

If you are an engineer embedding Cloudflare's API in Python, especially inside CI/CD pipelines or infrastructure automation that depends on cloudflare-python, it is worth checking early whether this beta breaks anything in your code.