Releasesby Glyph
January 2026 Documentation Changes
January 2026 Documentation Changes
Also shipped Jan 1, 2026Fastly in January 2026 →
`INVALID_BILLING_ADDRESS`: new processing error for subscription billing attempts
We've added a new processing error for subscription billing attempts: INVALID_BILLING_ADDRESS . This error is returned when one or more fields in the billing address contain invalid data. Validated fields include: firstName or lastName address1 or address2 city province or provinceCode country or countryCode zip (postal code) phone company
Subscription billing attempts throttling
Beginning in API version 2026-01, billing attempts will be throttled based on internal trust metrics to prevent abuse. If an attempt is throttled, it will be visible in the new throttled error code on the BillingAttemptUserErrorCode enum.
Workers - Build microfrontend applications on Workers
You can now deploy microfrontends to Cloudflare, splitting a single application into smaller, independently deployable units that render as one cohesive application. This lets different teams using different frameworks develop, test, and deploy each microfrontend without coordinating releases.
Access transactions on the Return object
You can now access transaction data directly from the Return object in the Admin GraphQL API. This new transactions connection simplifies your ability to associate payments and refunds with specific returns, removing the need to deduce relationships based on amounts and timestamps.
New Return Reason Definitions API for Better Return Insights
You can now use the new ReturnReasonDefinition type to capture more granular, category-specific return reasons when managing returns. This replaces the previous ReturnReason enum with a richer data model that helps provide merchants with better insights in their return analytics, and more tailored return experiences for their buyers.
Introducing the `orders/link_requested` webhook topic
Starting with API version 2026-01 of the GraphQL Admin API, your app can subscribe to the orders/link_requested webhook topic. This webhook is triggered when a customer requests a new order link from an expired Order status page, allowing your app to be notified when customers need access to their order details after the original link has expired.