API Breaking Changes and Deprecations — March 2026

Service Key authentication has been deprecated. Users should update their authentication methods to avoid future issues.

Service Key authentication has been deprecated. Users should review their authentication methods and plan for migration away from Service Keys to avoid future disruptions.

Service Key authentication has been deprecated. Users should review their authentication methods and plan for migration away from Service Keys.

Service Key authentication has been deprecated. Users should migrate to alternative authentication methods to avoid future issues.

Service Key authentication has been deprecated. Users should migrate to alternative authentication methods to avoid future issues.

The Datadog Agent no longer uses `datadog.*` namespaced span attributes (except `datadog.host.name` and `datadog.container.tag.*`) for constructing Datadog span fields, relying solely on standard OpenTelemetry semantic conventions. The configuration option `otlp_config.traces.ignore_missing_datadog_fields` is also deprecated and has no effect, requiring users to migrate to standard OTel attributes if they were using the `datadog.*` attributes.

Support for macOS 11 has been discontinued, making macOS 12 the new minimum supported version. Users on macOS 11 will need to upgrade their operating system to continue using the API.

Imagen models are deprecated and will be shut down on June 24, 2026. Users must migrate to Gemini Image models (e.g., gemini-2.5-flash-image) to avoid service disruption, as requests to shutdown models will return a 404 error.

Firebase Studio is being sunset on March 22, 2027. Users must migrate their projects to Google AI Studio or Google Antigravity to continue building, though existing deployed apps and core Firebase products are unaffected.

Firebase Studio is being sunset on March 22, 2027, requiring migration to Google AI Studio or Google Antigravity. Additionally, several Firebase SDKs (Android, JavaScript, Admin Python, Admin .NET) have been updated, and a new Firestore enterprise skill is available.

GitHub is deprecating security-related organization API fields, which will require users to update their integrations to avoid future disruptions. Additionally, Gemini 3 Pro and Copilot features have been retired.

The 'Code Quality permissions' have been removed from the 'security manager role'. This is a breaking change as it alters existing role capabilities, potentially requiring adjustments to security management workflows.

The cost center integration on the enterprise People page is being deprecated and was retired on March 16. Users should plan to migrate away from this feature.

GitHub Copilot is deprecating the Gemini 3 Pro and GPT-5.1 models. Users should be aware of this upcoming change and plan for migration to supported models.

Cloud Composer 2 environments can no longer be created in the Melbourne region (australia-southeast2) as it will now only support Cloud Composer 3 environments. Existing Cloud Composer 2 environments in this region are unaffected.

Google Cloud Contact Center as a Service's Web SDK version 2 will be shut down on June 26, 2026, and will no longer function. Users must upgrade to Web SDK v3 before this date to avoid breaking their integration.

Several Imagen generation GA endpoints on Generative AI on Vertex AI have been deprecated. Users are recommended to update their model endpoints to 'gemini-2.5-flash-image' before June 30, 2026, to avoid service disruption.

Operations on Compute Engine instance boot disks with attached service accounts, such as creating snapshots or cloning, now require the `iam.serviceAccounts.actAs` permission on the service account. This is a breaking change that may cause existing workflows to fail if permissions are not updated.

Google Kubernetes Engine (GKE) has updated available cluster versions across Rapid, Regular, and Stable channels. Several older versions have been deprecated and will be removed in 90 days, or at the end of support, if sooner, requiring users to upgrade their clusters.

Hive Metastore versions 1.2.2 and 2.2.0 are deprecated for Dataproc Metastore. Users can no longer create new services with these versions, though existing services will continue to function.

The `prompt_cache_key` parameter has been removed from API responses and the `phase` field has been removed from message types. This is a breaking change that may require updates to client code that relies on these fields.

This release introduces the new gpt-5.4 model and new tool capabilities (search, computer). It also includes breaking changes by removing the `prompt_cache_key` parameter from responses and the `phase` field from message types, though `phase` was later re-added.

Version 5.1.X removes features that were deprecated in version 5.0. This is a breaking change that may cause existing integrations to fail if they relied on these removed features.

This release includes several breaking changes and deprecations. The `display_message` field in webhooks will now return `null` instead of being omitted. New customers must use the Stripe Payment Intents API, and existing customers using Charges and Sources are impacted. The `consumer_report_permissible_purpose` field will become mandatory for Consumer Report Link tokens, and a migration to new User APIs is beginning. Additionally, a mandatory migration to a new Bank of America API is underway, requiring users to go through update mode to avoid disconnections.

This release includes several breaking changes and deprecations, including the migration off older Stripe Charges and Sources API, a new mandatory field for Plaid Check Consumer Report, and a required migration for Bank of America API. Users must update their integrations to avoid service disruptions.

Plaid is deprecating the Stripe Charges and Sources API for new integrations and migrating existing users. The `consumer_report_permissible_purpose` field will become mandatory for Consumer Report products, and Bank of America API is migrating, requiring existing items to go through update mode by late October 2026.

The `--force` flag in Shopify CLI for app releases is deprecated and will be removed in May 2026. Developers should update their CI/CD scripts to use `--allow-updates` to prevent accidental app extension deletions.

The `pre_tax_price` fields have been removed from the Order REST Admin API. Developers must now use the GraphQL Admin API for order line item pricing, which will cause existing integrations relying on these fields to break.

Starting April 1, 2026, new public apps using the Admin API must implement expiring offline access tokens for enhanced security. This is a mandatory change for new public apps and will require developers to update their authentication flows.

The Payments Apps API has deprecated the 'RISKY' rejection reason code. Developers should now use 'FRAUD_SUSPECTED' instead to provide precise feedback to merchants.

Fields in ShopifyQL analytics are deprecated and replaced with renamed versions (e.g., sales reversals) in API version 2026-04 to better reflect all order adjustments. Users should update their queries before the old fields are removed.

ShopifyQL returns fields in analytics are deprecated and replaced with renamed versions (e.g., sales reversals) in API version 2026-04. Developers should update their queries before these fields are removed to ensure continued functionality and accurate reporting.

Shopify has updated its requirements, mandating that all apps process refunds exclusively through the original payment processor. Apps should use 'refundCreate' or 'returnProcess' for store credits to comply with this new secure and consistent handling within Shopify.

The `inventorySetScheduledChanges` mutation and the `InventoryLevel.scheduledChanges` field are being removed in API version 2026-07 with no direct replacement, requiring developers to update their apps to prevent disruptions. For immediate inventory updates, `inventoryAdjustQuantities` is suggested.

The 'id' field has been removed from checkout webhooks and the 'checkout_id' field from order webhooks as of API version 2026-04. Developers must now use the checkout token to reference checkouts, which will require code changes to avoid breaking existing integrations.

Legacy customer accounts are no longer available for new stores, and merchants are advised to upgrade. Additionally, bare query strings in URLs will no longer bust the cache for assets, requiring the use of Liquid filters for asset refreshing.

The Stripe API introduces several breaking changes, including updates to card property requirements, removal of deprecated methods, and renaming of attributes. Additionally, some features and fields are deprecated, requiring developers to update their integrations to avoid failures.

Access to the OpenAPI spec via the anonymous key is deprecated and will require a service role or secret API key after March 11. This change affects how the OpenAPI schema endpoint is accessed but does not impact existing data API usage.

Access to the OpenAPI spec via the anonymous key has been deprecated and will require a service role or secret API key after March 11. This change affects how the schema endpoint is accessed but does not impact existing data API usage.

Vercel will remove support for the legacy DHE-RSA-AES256-GCM-SHA384 cipher suite on June 30th, 2026. Clients using TLS 1.2 with this cipher suite will no longer be able to connect to the Vercel network and should update their configurations to use one of the supported cipher suites.

Vercel will remove support for the legacy DHE-RSA-AES256-GCM-SHA384 cipher suite on June 30th, 2026. Clients using TLS 1.2 with this cipher will no longer be able to connect, potentially impacting automated systems or clients with non-standard TLS configurations.

Vercel will remove support for the legacy DHE-RSA-AES256-GCM-SHA384 cipher suite on June 30th, 2026. Clients using TLS 1.2 with this cipher suite will no longer be able to connect, requiring verification of supported cipher suites for automated systems and integrations.

Vercel will remove support for the legacy DHE-RSA-AES256-GCM-SHA384 cipher suite on June 30th, 2026. Clients using this cipher suite for TLS 1.2 connections will no longer be able to connect to the Vercel network after this date, potentially impacting automated systems and older HTTP clients.