Update generated code for beta

.hark/changes/2026-09-11_xavdid_singleton-related-object.change.md

@@ -0,0 +1,7 @@
+---
+title: Support `EventNotification`s with singleton related objects
+pr_url: https://github.com/stripe/stripe-python/pull/1904
+jira_tickets_closed:
+- RUN_DEVSDK-2825
+released_in_version: 16.0.0
+---

.hark/changes/2026-09-15_zacchua_add-stripe-suppress-notices.change.md

@@ -0,0 +1,8 @@
+---
+title: Allow suppressing Stripe notices
+pr_url: https://github.com/stripe/stripe-python/pull/1909
+semver_level: minor
+released_in_version: 16.0.0
+---
+
+Set the `STRIPE_SUPPRESS_NOTICES` environment variable to `true` to suppress Stripe notices in test and sandbox environments when not running under a detected AI agent. Notices remain enabled by default and continue to be shown to AI agents.

.hark/changes/2026-09-16_zacchua_fix-event-handler-account-scoping.change.md

@@ -0,0 +1,9 @@
+---
+title: Fix account scoping for event notification handler callback clients
+pr_url: https://github.com/stripe/stripe-python/pull/1911
+semver_level: patch
+released_in_version: 16.0.0
+---
+
+- Fix callback clients to use the event's Stripe context and preserve the original client's non-account configuration.
+- Fix API errors when using an event notification handler with a client configured with a Stripe account.

.hark/changes/2026-09-17_zacchua_remove-deprecated-stripeobject-request.change.md

@@ -0,0 +1,8 @@
+---
+title: Remove deprecated `StripeObject.request()` method
+pr_url: https://github.com/stripe/stripe-python/pull/1914
+semver_level: major
+released_in_version: 16.0.0
+---
+
+The deprecated `StripeObject.request()` method has been removed. Use `StripeClient.raw_request()` to make custom API requests.

.hark/changes/2026-09-17_zacchua_rename-reversal-transferreversal.change.md

@@ -0,0 +1,8 @@
+---
+title: Rename `stripe.Reversal` to `stripe.TransferReversal`
+pr_url: https://github.com/stripe/stripe-python/pull/1915
+semver_level: major
+released_in_version: 16.0.0
+---
+
+- ⚠️ Rename the `stripe.Reversal` resource class to `stripe.TransferReversal`. Update references and type annotations to use `stripe.TransferReversal`.

.hark/changes/2026-09-18_markisaackogan_mark-path-params-as-positional-only.change.md

@@ -0,0 +1,10 @@
+---
+title: Make path parameters positional-only in all service methods
+pr_url: https://github.com/stripe/stripe-python/pull/1920
+semver_level: major
+released_in_version: 16.0.0
+---
+
+Path parameters must now be passed positionally to service methods. Passing them by keyword is no longer supported. This prevents parameter names derived from the API specification from becoming part of the public interface.
+
+ Resource methods are unaffected by this change.

.hark/changes/2026-09-23_markisaackogan_mark-overloaded-params-as-positional-only.change.md

@@ -0,0 +1,8 @@
+---
+title: Make path parameters positional-only in all service methods
+pr_url: https://github.com/stripe/stripe-python/pull/1924
+semver_level: major
+released_in_version: 16.0.0
+---
+
+Path parameters must now be passed positionally on resource methods that support both classmethod and instance-method call styles (e.g. Coupon.delete). Passing them by keyword is no longer supported.

.hark/changes/2026-10-02_stripe-openapi_9b0360e2.change.md

@@ -0,0 +1,8 @@
+---
+title: Update generated code
+pr_url: https://github.com/stripe/stripe-python/pull/1938
+semver_level: minor
+is_stripe_api_change: true
+---
+
+* Release specs are identical.

.hark/migration-guides/v16.md

@@ -0,0 +1,80 @@
+# Migration guide for v16
+
+This version of the SDK uses API version `2026-09-30.endive`. If the format of this API version looks new to you, see our new [API release process](https://stripe.com/blog/introducing-stripes-new-api-release-process).
+
+Please review our API changelog for [`2026-09-30.endive`](https://docs.stripe.com/changelog/2026-09-30.endive) to understand all the breaking changes to the Stripe API, the reasons behind them and potential alternatives.
+
+The Python SDK specific [changelog for v16](https://github.com/stripe/stripe-python/blob/master/CHANGELOG.md#16-0-0) has the corresponding changes in the SDKs as well as SDK specific breaking changes.
+
+<!-- This is the migration guide for the next major version!
+If you're making breaking changes, add a new h2 header with a nice title and write a detailed guide to help users upgrade.
+You will almost certainly need before/after code examples and information about which users this change affects.
+See: https://github.com/stripe/hark#writing-a-great-migration-guide
+-->
+
+## Rename `stripe.Reversal` to `stripe.TransferReversal`
+
+The class representing a transfer reversal has been renamed from `stripe.Reversal` to `stripe.TransferReversal`.
+
+This change affects integrations that reference `stripe.Reversal` directly, including imports, class comparisons, `isinstance` checks, and type annotations. Replace those references with `stripe.TransferReversal`:
+
+```python
+# Before
+reversal = stripe.Transfer.retrieve_reversal("tr_123", "trr_123")
+isinstance(reversal, stripe.Reversal)
+
+# After
+reversal = stripe.Transfer.retrieve_reversal("tr_123", "trr_123")
+isinstance(reversal, stripe.TransferReversal)
+```
+
+The methods for creating, retrieving, modifying, and listing transfer reversals have not changed. Code that only calls those methods and reads attributes from the returned object does not require an update.
+
+## `StripeObject.request()` has been removed
+
+The deprecated `StripeObject.request()` method has been removed. If you used it to make custom API requests, create a `StripeClient` and use `raw_request()` instead:
+
+```python
+# Before
+response = stripe_object.request("get", "/v1/example")
+
+# After
+client = stripe.StripeClient("sk_test_...")
+response = client.raw_request("get", "/v1/example")
+```
+
+## Path parameters must now be passed positionally
+
+Path parameters must now be passed positionally instead of by keyword.
+
+For example, a customer ID that was previously accepted as a keyword argument:
+
+```python
+customer = client.v1.customers.retrieve(customer="cus_123")
+```
+
+must now be passed positionally:
+
+```python
+customer = client.v1.customers.retrieve("cus_123")
+```
+
+This also affects legacy resource methods that support both classmethod and instance-method call styles. For example, `Customer.retrieve_payment_method`:
+
+```python
+# Before
+payment_method = customer.retrieve_payment_method(
+    payment_method="pm_123"
+)
+payment_method = stripe.Customer.retrieve_payment_method(
+    customer="cus_123", payment_method="pm_123"
+)
+
+# After
+payment_method = customer.retrieve_payment_method("pm_123")
+payment_method = stripe.Customer.retrieve_payment_method(
+    "cus_123", "pm_123"
+)
+```
+
+Update calls to your methods to pass path parameters before any request parameters or options.

CODEGEN_VERSION

@@ -1 +1 @@
-588801ef34f7b5f7d6a784d3354f5f93d2a26ffb
+f13165446935a574483f0ba6243fc05b50669dc6

OPENAPI_VERSION

@@ -1 +1 @@
-v2526
+v2532