whop_sdk 2.4.0 → 2.5.0

data/reference.md

@@ -12,7 +12,7 @@
 <dl>
 <dd>
 
-Create a short-lived access token for authenticating API requests. When using API key authentication, provide account_id or user_id. When using OAuth, the user is derived from the token. Use this token with Whop's web and mobile embedded components.
+Creates a short-lived access token for Whop's web and mobile embedded components. With API key authentication, pass `account_id` or `user_id`; with OAuth, the token is issued for the OAuth user.
 </dd>
 </dl>
 </dd>
@@ -99,7 +99,7 @@ client.access_tokens.create
 <dl>
 <dd>
 
-Generate a URL that directs a sub-merchant to their account portal, such as the hosted payouts dashboard or the KYC onboarding flow.
+Generates a URL that sends a sub-merchant to a hosted Whop page, such as the payouts dashboard or the KYC onboarding flow. Requires an API key.
 </dd>
 </dl>
 </dd>
@@ -191,7 +191,7 @@ client.account_links.create(
 <dl>
 <dd>
 
-Lists accounts visible to the credential. User tokens return the user's business accounts; Account API keys return the requesting account and its connected accounts. Pass `parent_account_id` to return only that parent account's connected accounts. Includes each account's `cards` application summary when the caller has `company:balance:read` access to that account.
+Lists accounts visible to the credential. User tokens return the user's business accounts; Account API keys return the requesting account and its connected accounts.
 </dd>
 </dl>
 </dd>
@@ -545,7 +545,7 @@ client.accounts.me
 <dl>
 <dd>
 
-Retrieves a single account by ID or public route when it is visible to the credential, including its crypto wallet. The reserved id `me` retrieves the account associated with the current Account API key; user tokens have no single account, so they must address one by ID or route.
+Retrieves an account visible to the credential by ID or public route, including its crypto wallet.
 </dd>
 </dl>
 </dd>
@@ -575,7 +575,7 @@ client.accounts.retrieve(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — Account ID, prefixed `biz_`, its public route, or `me` for the account associated with the current API key.
+**id:** `String` — Account ID, prefixed `biz_`, its public route, or `me` for the account associated with the current Account API key. User tokens have no single account, so they cannot use `me`.
     
 </dd>
 </dl>
@@ -677,7 +677,7 @@ client.accounts.delete(id: "id")
 <dl>
 <dd>
 
-Updates an account. User tokens can update business accounts; Account API keys can update connected accounts. The reserved id `me` — accepted on Retrieve Account — resolves to the requesting account, which an Account API key cannot edit, so updates must name the connected account by its `biz_` id.
+Updates an account. User tokens can update business accounts; Account API keys can update connected accounts.
 </dd>
 </dl>
 </dd>
@@ -707,7 +707,7 @@ client.accounts.update(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — Account ID, prefixed `biz_`.
+**id:** `String` — Account ID, prefixed `biz_`. The reserved id `me` resolves to the requesting account, which an Account API key cannot edit.
     
 </dd>
 </dl>
@@ -755,14 +755,6 @@ client.accounts.update(id: "id")
 <dl>
 <dd>
 
-**business_type:** `String` — High-level business category for the account. See the [business types and industries glossary](/api-reference/beta/accounts/account#business-types-and-industries-glossary) for valid values.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **cancellation_policy:** `Whop_sdk::Accounts::Types::UpdateAccountsRequestCancellationPolicy` — The account's cancellation policy document. Attached to new disputes as the cancellation policy evidence, with the terms of service as the fallback. PDF only. Pass a JSON object containing an `id` from [Create File](/api-reference/files/create-file), or `null` to remove it.
     
 </dd>
@@ -827,22 +819,6 @@ client.accounts.update(id: "id")
 <dl>
 <dd>
 
-**industry_group:** `String` — Account industry group. See the [business types and industries glossary](/api-reference/beta/accounts/account#business-types-and-industries-glossary) for valid values.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**industry_type:** `String` — Specific industry vertical for the account. See the [business types and industries glossary](/api-reference/beta/accounts/account#business-types-and-industries-glossary) for valid values.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **invoice_prefix:** `String` — Prefix used for account invoices.
     
 </dd>
@@ -1091,6 +1067,14 @@ client.accounts.update(id: "id")
 <dl>
 <dd>
 
+**industry_type:** `Object` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **request_options:** `Whop_sdk::Accounts::RequestOptions` 
     
 </dd>
@@ -1115,7 +1099,7 @@ client.accounts.update(id: "id")
 <dl>
 <dd>
 
-Starts an LLC or C-Corp formation for a business account. Defaults to an LLC; set `entity_type` to `c_corp` to form a C-Corp, which additionally requires `share_structure` and officer `roles` on every founder. On submission, the application is validated and the response returns a hosted checkout URL. Once paid, the filing is submitted. Track progress through the account's [`company_formation`](/api-reference/beta/accounts/retrieve-account) field on Retrieve Account.
+Starts an LLC or C-Corp formation for a business account. The application is validated and the response returns a hosted checkout URL; once paid, the filing is submitted. Track progress through the account's [`company_formation`](/api-reference/beta/accounts/retrieve-account) field on Retrieve Account.
 </dd>
 </dl>
 </dd>
@@ -1142,7 +1126,6 @@ client.accounts.form_company(
   },
   business_name: "Shine Time Auto Detailing",
   business_phone: "+15125550142",
-  business_type: "brick_and_mortar",
   business_website: "https://shinetime.example",
   entity_suffix: "LLC",
   entity_type: "llc",
@@ -1167,8 +1150,6 @@ client.accounts.form_company(
     roles: ["president"],
     ssn: "123-45-6789"
   }],
-  industry_group: "automotive",
-  industry_type: "car_wash",
   share_structure: {
     number_of_shares: 123,
     value: 123
@@ -1221,14 +1202,6 @@ client.accounts.form_company(
 <dl>
 <dd>
 
-**business_type:** `String` — High-level business category, from the Whop business taxonomy. Valid values are listed on [business types and industries glossary](/api-reference/beta/accounts/account#business-types-and-industries-glossary).
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **business_website:** `String` — Company website URL.
     
 </dd>
@@ -1277,22 +1250,6 @@ client.accounts.form_company(
 <dl>
 <dd>
 
-**industry_group:** `String` — Industry group, from the Whop business taxonomy. Valid values are listed on [business types and industries glossary](/api-reference/beta/accounts/account#business-types-and-industries-glossary).
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**industry_type:** `String` — Specific industry vertical, from the Whop business taxonomy. Valid values are listed on [business types and industries glossary](/api-reference/beta/accounts/account#business-types-and-industries-glossary).
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **share_structure:** `Whop_sdk::Accounts::Types::FormCompanyAccountsRequestShareStructure` — Authorized share structure. Required when `entity_type` is `c_corp`; ignored for LLCs.
     
 </dd>
@@ -1333,7 +1290,7 @@ client.accounts.form_company(
 <dl>
 <dd>
 
-Queues one background retry of the account's failed ads payments across its campaigns, using the account's configured ads payment methods. A queued response does not mean payment succeeded. Read campaign delivery_status and issues for the outcome. Successful settlement clears the payment block without changing configured active or paused status; legacy payment_failed status becomes paused. Another request while the account retry is queued or running returns an error asking you to wait.
+Queues one background retry of the account's failed ads payments across its campaigns, using the account's configured ads payment methods. A queued response does not mean payment succeeded; read each campaign's `delivery_status` and `issues` for the outcome. Successful settlement clears the payment block without changing a configured `active` or `paused` status; a legacy `payment_failed` status becomes `paused`. Returns an error when the account has no failed ads payments, or while a previous retry for the account is queued or running.
 </dd>
 </dl>
 </dd>
@@ -1363,7 +1320,7 @@ client.accounts.retry_ads_payment(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — The account ID.
+**id:** `String` — Account ID, prefixed `biz_`.
     
 </dd>
 </dl>
@@ -1506,6 +1463,14 @@ client.accounts.transfer_ownership(
 <dl>
 <dd>
 
+**authorized_user_id:** `String` — Your team membership on the business this referral is made for, prefixed `ausr_`. The referral then credits that team instead of you personally. Requires `as_partner`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **identifier:** `String` — The user to transfer ownership to: a user ID (`user_*`) or an email address. An email address with no Whop account yet is sent an invite to create one.
     
 </dd>
@@ -1729,7 +1694,7 @@ client.ad_campaigns.list
 <dl>
 <dd>
 
-Creates an ad campaign for an account.
+Creates an ad campaign in `draft` status for an account. Nothing runs until you launch it by setting `status` to `active` with `PATCH /ad_campaigns/:id`.
 </dd>
 </dl>
 </dd>
@@ -2055,7 +2020,7 @@ client.ad_campaigns.delete(id: "id")
 <dl>
 <dd>
 
-Updates an ad campaign's editable fields (title, budget, schedule, bid strategy, special ad categories, and, before launch, budget type and budget optimization), and launches a draft campaign by setting status to active. Objective and desired cost per result are fixed at creation and cannot be changed.
+Updates an ad campaign's settings, or launches a draft campaign by setting `status` to `active`. The objective and desired cost per result are fixed at creation and cannot be changed.
 </dd>
 </dl>
 </dd>
@@ -2416,7 +2381,7 @@ client.ad_campaigns.unpause(id: "id")
 <dl>
 <dd>
 
-List saved rules the caller can read. Filter by business with account_id.
+Lists the conversion value rules you can read.
 </dd>
 </dl>
 </dd>
@@ -2446,7 +2411,7 @@ client.ad_conversion_value_rules.list
 <dl>
 <dd>
 
-**account_id:** `String` 
+**account_id:** `String` — Only rules belonging to this account, prefixed `biz_`.
     
 </dd>
 </dl>
@@ -2550,7 +2515,7 @@ client.ad_conversion_value_rules.list
 <dl>
 <dd>
 
-Create one rule covering every selected target and event combination. Active rules cannot overlap for the same platform and event. Customer prices and Whop revenue stay unchanged.
+Creates one rule covering every selected target and event combination. Active rules cannot overlap for the same platform and event. Customer prices and Whop revenue stay unchanged.
 </dd>
 </dl>
 </dd>
@@ -2638,7 +2603,7 @@ client.ad_conversion_value_rules.create(
 <dl>
 <dd>
 
-**replace_rule_ids:** `Internal::Types::Array[String]` — Exact IDs of active rules whose overlapping selections will be replaced. Other selections keep their values; remaining selections may split into separate rules. Broader rules remain as fallbacks for other items. Stale or incomplete conflict selections fail.
+**replace_rule_ids:** `Internal::Types::Array[String]` — Exact IDs of active rules whose overlapping selections will be replaced. Other selections keep their values; remaining selections may split into separate rules. Broader rules remain as fallbacks for other items. Rules left with no selections are paused. Stale or incomplete conflict selections fail.
     
 </dd>
 </dl>
@@ -2678,6 +2643,20 @@ client.ad_conversion_value_rules.create(
 <dl>
 <dd>
 
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Retrieves a conversion value rule with its targets, events, and value adjustment.
+</dd>
+</dl>
+</dd>
+</dl>
+
 #### 🔌 Usage
 
 <dl>
@@ -2702,7 +2681,7 @@ client.ad_conversion_value_rules.retrieve(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — Conversion value rule ID.
+**id:** `String` — Conversion value rule ID, prefixed `adcvr_`.
     
 </dd>
 </dl>
@@ -2734,7 +2713,7 @@ client.ad_conversion_value_rules.retrieve(id: "id")
 <dl>
 <dd>
 
-Soft-delete a rule and deactivate all its coverage. Preserve its stored settings.
+Deletes a rule and deactivates all its coverage. The rule's stored settings are preserved.
 </dd>
 </dl>
 </dd>
@@ -2764,7 +2743,7 @@ client.ad_conversion_value_rules.delete(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — Conversion value rule ID.
+**id:** `String` — Conversion value rule ID, prefixed `adcvr_`.
     
 </dd>
 </dl>
@@ -2796,7 +2775,7 @@ client.ad_conversion_value_rules.delete(id: "id")
 <dl>
 <dd>
 
-Edit a rule without changing its status. Supplied targets or events replace that selection in full. Omitted fields stay unchanged. All changes succeed or fail together.
+Edits a rule without changing its status. Supplied `targets` or `events` replace that selection in full, and omitted fields stay unchanged. All changes succeed or fail together.
 </dd>
 </dl>
 </dd>
@@ -2826,7 +2805,7 @@ client.ad_conversion_value_rules.update(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — Conversion value rule ID.
+**id:** `String` — Conversion value rule ID, prefixed `adcvr_`.
     
 </dd>
 </dl>
@@ -2874,7 +2853,7 @@ client.ad_conversion_value_rules.update(id: "id")
 <dl>
 <dd>
 
-**replace_rule_ids:** `Internal::Types::Array[String]` — Exact IDs of active rules whose overlapping selections will be replaced. Other selections keep their values; remaining selections may split into separate rules. Broader rules remain as fallbacks for other items. Stale or incomplete conflict selections fail.
+**replace_rule_ids:** `Internal::Types::Array[String]` — Exact IDs of active rules whose overlapping selections will be replaced. Other selections keep their values; remaining selections may split into separate rules. Broader rules remain as fallbacks for other items. Rules left with no selections are paused. Stale or incomplete conflict selections fail.
     
 </dd>
 </dl>
@@ -2914,7 +2893,7 @@ client.ad_conversion_value_rules.update(id: "id")
 <dl>
 <dd>
 
-Pause the rule across all selected targets and events.
+Pauses the rule across all selected targets and events.
 </dd>
 </dl>
 </dd>
@@ -2944,7 +2923,7 @@ client.ad_conversion_value_rules.pause(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — Conversion value rule ID.
+**id:** `String` — Conversion value rule ID, prefixed `adcvr_`.
     
 </dd>
 </dl>
@@ -2976,7 +2955,7 @@ client.ad_conversion_value_rules.pause(id: "id")
 <dl>
 <dd>
 
-Resume the rule and automatically replace overlapping selections in the same transaction. Other selections keep their values, and broader rules remain as defaults. Rules with no remaining selections are paused. Resuming an already-active rule makes no changes.
+Resumes the rule and automatically replaces overlapping selections in the same transaction. Other selections keep their values, and broader rules remain as defaults. Rules with no remaining selections are paused. Resuming an already-active rule makes no changes.
 </dd>
 </dl>
 </dd>
@@ -3006,7 +2985,7 @@ client.ad_conversion_value_rules.unpause(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — Conversion value rule ID.
+**id:** `String` — Conversion value rule ID, prefixed `adcvr_`.
     
 </dd>
 </dl>
@@ -3510,7 +3489,7 @@ Valid positions per platform:
 <dl>
 <dd>
 
-Estimates how many people a draft targeting spec can reach, before an ad group is created. The body takes the same targeting fields as creating an ad group — `regions`, `demographics`, `detailed_targeting`, `audiences`, `languages`, and `devices` — and nothing is persisted.
+Estimates how many people a draft targeting spec can reach, before an ad group is created. The body takes the same targeting fields as creating an ad group, and nothing is persisted.
 </dd>
 </dl>
 </dd>
@@ -3628,7 +3607,7 @@ client.ad_groups.estimate_reach(platform: "meta")
 <dl>
 <dd>
 
-Searches the ad platform's targeting taxonomy for options to target an ad group with. Each result comes back in the exact shape the ad-group body accepts for its `type`, so it can be used in `detailed_targeting`, `regions`, or `languages` as-is. A blank `query` browses the small fixed lists (behaviors, browse demographic categories, languages); interests, work employers, job titles, schools, majors, and locations need a search term.
+Searches the ad platform's targeting taxonomy for options to target an ad group with. Each result comes back in the exact shape the ad-group body accepts for its `type`, so it can be used in `detailed_targeting`, `regions`, or `languages` as-is.
 </dd>
 </dl>
 </dd>
@@ -3674,7 +3653,7 @@ client.ad_groups.search_targeting_options(platform: "meta")
 <dl>
 <dd>
 
-**query:** `String` — The search term. Blank browses the fixed lists; interests, work employers, job titles, schools, majors, and locations return nothing without one.
+**query:** `String` — The search term. Blank browses the small fixed lists (behaviors, browse demographic categories, and languages); interests, work employers, job titles, schools, majors, and locations return nothing without one.
     
 </dd>
 </dl>
@@ -3746,7 +3725,7 @@ client.ad_groups.search_targeting_options(platform: "meta")
 <dl>
 <dd>
 
-Retrieves a single ad group.
+Retrieves an ad group, with performance stats for the window set by `stats_from` and `stats_to`.
 </dd>
 </dl>
 </dd>
@@ -3840,7 +3819,7 @@ client.ad_groups.retrieve(id: "id")
 <dl>
 <dd>
 
-Deletes an ad group.
+Deletes an ad group, removing it from the ad platform so it stops delivering.
 </dd>
 </dl>
 </dd>
@@ -4175,7 +4154,7 @@ Valid positions per platform:
 <dl>
 <dd>
 
-Creates copies of the ad group in `duplicating` status and returns them — into its own campaign, or into target_ad_campaign_id (which must belong to the same account and be compatible with the ad group's targeting and goals); each copy transitions to its final status (matching the source's active/paused state) once duplication completes. Poll each returned ad group until it leaves `duplicating` — a copy that could not be completed is deleted and returns 404.
+Starts copying an ad group and returns the copies in `duplicating` status. Poll each returned ad group until it leaves `duplicating`: it then takes the source's `active` or `paused` status, or, if the copy could not be completed, is deleted and returns 404.
 </dd>
 </dl>
 </dd>
@@ -4229,7 +4208,7 @@ client.ad_groups.duplicate(id: "id")
 <dl>
 <dd>
 
-**target_ad_campaign_id:** `String` — Campaign to duplicate into. Defaults to the ad group's own campaign.
+**target_ad_campaign_id:** `String` — Campaign to duplicate into. Must belong to the same account and be compatible with the ad group's targeting and goals. Defaults to the ad group's own campaign.
     
 </dd>
 </dl>
@@ -5556,7 +5535,7 @@ client.ads.update(id: "id")
 <dl>
 <dd>
 
-Copies the ad into its own ad group, or into target_ad_group_id (which must belong to the same account and be compatible with the ad). Copies keep the source ad's active/paused state.
+Copies an ad into its own ad group or into another one. Copies keep the source ad's active or paused state.
 </dd>
 </dl>
 </dd>
@@ -5610,7 +5589,7 @@ client.ads.duplicate(id: "id")
 <dl>
 <dd>
 
-**target_ad_group_id:** `String` — Ad group to duplicate into. Defaults to the ad's own ad group.
+**target_ad_group_id:** `String` — Ad group to duplicate into, which must belong to the same account and be compatible with the ad. Defaults to the ad's own ad group.
     
 </dd>
 </dl>
@@ -5767,7 +5746,7 @@ client.ads.unpause(id: "id")
 <dl>
 <dd>
 
-Returns a paginated list of affiliates for the actor in context, with optional filtering by status, search, and sorting.
+Lists the affiliates of an account.
 
 Required permissions:
  - `affiliate:basic:read`
@@ -5900,7 +5879,7 @@ client.affiliates.list(
 <dl>
 <dd>
 
-Creates or finds an affiliate for a company and user.
+Creates an affiliate for a user on an account. If the user is already an affiliate of the account, returns that affiliate, reactivating it if it was archived.
 
 Required permissions:
  - `affiliate:create`
@@ -6041,7 +6020,7 @@ client.affiliates.retrieve(id: "aff_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Archives an existing Affiliate
+Archives an affiliate. The affiliate that handles Whop marketplace referrals cannot be archived.
 
 Required permissions:
  - `affiliate:update`
@@ -6106,7 +6085,7 @@ client.affiliates.archive(id: "aff_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Unarchives an existing Affiliate
+Unarchives an archived affiliate.
 
 Required permissions:
  - `affiliate:update`
@@ -6859,7 +6838,7 @@ client.api_keys.create(
 <dl>
 <dd>
 
-Lists the catalog of permission actions that can be granted to users, apps, and API keys — the source for the dashboard's permission pickers. Small and returned in full on one page.
+Lists the catalog of permission actions that can be granted to users, apps, and API keys. Use it to choose the `permissions` for an API key or to build a permission picker. Small and returned in full on one page.
 </dd>
 </dl>
 </dd>
@@ -7471,7 +7450,7 @@ client.app_builds.list(app_id: "app_id")
 <dl>
 <dd>
 
-Uploads a new build artifact for an app. Upload the file first (POST /files or a direct upload), then reference it here; iOS and Android take a .zip bundle, web takes a JavaScript file or a .zip archive of the hosted site.
+Uploads a new build artifact for an app. Upload the file first with `POST /files` or a direct upload, then reference it in `attachment`.
 </dd>
 </dl>
 </dd>
@@ -7513,7 +7492,7 @@ client.app_builds.create(
 <dl>
 <dd>
 
-**attachment:** `Whop_sdk::AppBuilds::Types::CreateAppBuildsRequestAttachment` — The uploaded build file: `{ id }` for an existing file or `{ direct_upload_id }` for a completed direct upload.
+**attachment:** `Whop_sdk::AppBuilds::Types::CreateAppBuildsRequestAttachment` — The uploaded build file: pass `id` for an existing file or `direct_upload_id` for a completed direct upload. iOS and Android builds take a .zip bundle; web builds take a JavaScript file or a .zip archive of the hosted site.
     
 </dd>
 </dl>
@@ -7986,7 +7965,7 @@ client.apps.create(name: "Shine Time Booking")
 <dl>
 <dd>
 
-Retrieves an app by ID, claimed route, active verified custom hostname, or proxy domain id. Custom hostnames return 404 for inactive assignments, suspended accounts, or deleted apps. Credential fields (api_key, default_api_key, secrets) render `null` unless the caller has the corresponding developer permission on the owning account.
+Retrieves an app by ID, claimed route, active verified custom hostname, or proxy domain id. Authentication is optional; credential fields stay `null` unless you have the matching developer permission on the owning account.
 </dd>
 </dl>
 </dd>
@@ -8016,7 +7995,7 @@ client.apps.retrieve(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — App ID (prefixed `app_`). Retrieval also accepts the app's claimed route, an active verified custom hostname, or its proxy domain id.
+**id:** `String` — App ID (prefixed `app_`). Retrieval also accepts the app's claimed route, an active verified custom hostname, or its proxy domain id; a custom hostname returns `404` when its assignment is inactive, the owning account is suspended, or the app is deleted.
     
 </dd>
 </dl>
@@ -8078,7 +8057,7 @@ client.apps.delete(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — App ID (prefixed `app_`). Retrieval also accepts the app's claimed route, an active verified custom hostname, or its proxy domain id.
+**id:** `String` — App ID (prefixed `app_`). Retrieval also accepts the app's claimed route, an active verified custom hostname, or its proxy domain id; a custom hostname returns `404` when its assignment is inactive, the owning account is suspended, or the app is deleted.
     
 </dd>
 </dl>
@@ -8140,7 +8119,7 @@ client.apps.update(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — App ID (prefixed `app_`). Retrieval also accepts the app's claimed route, an active verified custom hostname, or its proxy domain id.
+**id:** `String` — App ID (prefixed `app_`). Retrieval also accepts the app's claimed route, an active verified custom hostname, or its proxy domain id; a custom hostname returns `404` when its assignment is inactive, the owning account is suspended, or the app is deleted.
     
 </dd>
 </dl>
@@ -8614,7 +8593,7 @@ client.apps.update_permissions(
 <dl>
 <dd>
 
-List custom and lookalike audiences for an account. Pass `audience_id` to return a specific audience.
+Lists an account's custom and lookalike audiences.
 </dd>
 </dl>
 </dd>
@@ -8716,7 +8695,7 @@ client.audiences.list(account_id: "account_id")
 <dl>
 <dd>
 
-Create an audience from a customer list, your account's Whop People data, or engagement with videos, lead forms, Instagram profiles, or Facebook pages. Create lookalike audiences to reach people similar to an existing audience. Processing runs asynchronously. Custom creation returns one audience; lookalike creation returns the requested similarity bands in `data`.
+Creates a custom audience from a customer list, your account's Whop People data, or engagement with videos, lead forms, Instagram profiles, or Facebook pages, or a lookalike audience that reaches people similar to an existing one. Processing runs asynchronously. A custom audience returns one audience; a lookalike returns the requested similarity bands in `data`.
 </dd>
 </dl>
 </dd>
@@ -9088,7 +9067,7 @@ client.audiences.add_people(
 <dl>
 <dd>
 
-Returns a paginated list of authorized team members for a company, with optional filtering by user, role, and creation date.
+Lists the authorized users on an account's team.
 
 Required permissions:
  - `company:authorized_user:read`
@@ -9225,7 +9204,7 @@ client.authorized_users.list(
 <dl>
 <dd>
 
-Add a new authorized user to a company.
+Adds a user to an account's team as an authorized user with the given role.
 
 Required permissions:
  - `authorized_user:create`
@@ -9393,7 +9372,7 @@ client.authorized_users.retrieve(id: "ausr_xxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Remove an authorized user from a company.
+Removes an authorized user from an account's team.
 
 Required permissions:
  - `authorized_user:delete`
@@ -10215,7 +10194,7 @@ client.bounty_submissions.list
 <dl>
 <dd>
 
-Creates a submission on a workforce bounty. Include a `deliverable` payload — any combination of links and uploaded files, with at least one of the two — and the submission goes straight to review; create is the only step. For `data_capture` bounties, omit the deliverable: this starts a claimed attempt whose proof accumulates server-side, and the separate submit endpoint sends it to review once complete. Requires a user credential — account API keys cannot author submissions.
+Creates a submission on a workforce bounty. Include a `deliverable` and the submission goes straight to review; create is the only step. For `data_capture` bounties, omit the deliverable: this starts a claimed attempt whose proof accumulates server-side, and `POST /bounty_submissions/:id/submit` sends it to review once complete. Requires a user credential — account API keys cannot author submissions.
 </dd>
 </dl>
 </dd>
@@ -10433,7 +10412,7 @@ client.bounty_submissions.delete(id: "id")
 <dl>
 <dd>
 
-Submits a claimed attempt for review. A livestream attempt needs an ended proof stream and can attach an optional `deliverable` — links, files, and a caption in any combination; if the attempt already went to review when its stream ended, the payload attaches to it once, until reviewers start voting. A data capture attempt instead needs enough validated clip time and takes no payload. Only the worker who started the attempt can submit it — account API keys cannot.
+Submits a claimed attempt for review. A livestream attempt needs an ended proof stream and can attach a `deliverable`; a data capture attempt instead needs enough validated clip time and takes no payload. Only the worker who started the attempt can submit it — account API keys cannot.
 </dd>
 </dl>
 </dd>
@@ -10471,7 +10450,7 @@ client.bounty_submissions.submit(id: "id")
 <dl>
 <dd>
 
-**deliverable:** `Whop_sdk::BountySubmissions::Types::SubmitBountySubmissionsRequestDeliverable` — Work to attach to the submission. Combine `urls`, `file_ids`, and `caption` freely; all are optional.
+**deliverable:** `Whop_sdk::BountySubmissions::Types::SubmitBountySubmissionsRequestDeliverable` — Work to attach to a livestream attempt. Combine `urls`, `file_ids`, and `caption` freely; all are optional. If the attempt already went to review when its stream ended, the deliverable attaches to it once, until reviewers start voting. Data capture attempts take no deliverable.
     
 </dd>
 </dl>
@@ -10504,7 +10483,7 @@ client.bounty_submissions.submit(id: "id")
 <dl>
 <dd>
 
-Lists the card transactions of an account or a user, newest first. Defaults to the account the credential belongs to. Covers every card the owner has ever had, including canceled cards and spend that predates a re-application, and team members only see transactions on the cards assigned to them. Pass `transaction_ids` to fetch specific transactions instead of paging for them.
+Lists the card transactions of an account or a user, newest first. Covers every card the owner has ever had, including canceled cards and spend that predates a re-application, and team members only see transactions on the cards assigned to them. Pass `transaction_ids` to fetch specific transactions instead of paging for them.
 </dd>
 </dl>
 </dd>
@@ -10674,7 +10653,7 @@ client.card_transactions.list(
 <dl>
 <dd>
 
-Fetches a single card transaction by its `citx_` identifier. The owner defaults to the account the credential belongs to.
+Retrieves a single card transaction from any card the owner has ever had, including canceled cards. Team members can retrieve only transactions on the cards assigned to them.
 </dd>
 </dl>
 </dd>
@@ -10823,7 +10802,7 @@ client.cards.list
 <dl>
 <dd>
 
-Issue a virtual card, or apply for card issuing. An account with no application files one here and gets back a `202`; call again to issue the card once it is approved.
+Issues a virtual card, or applies for card issuing. An account with no application files one here and gets back a `202`; call again to issue the card once it is approved.
 </dd>
 </dl>
 </dd>
@@ -10933,7 +10912,7 @@ client.cards.create
 <dl>
 <dd>
 
-Retrieve a single card.
+Retrieves a single card, including its `secrets` (card number, CVC, and PIN), which List Cards does not return.
 </dd>
 </dl>
 </dd>
@@ -11011,7 +10990,7 @@ client.cards.retrieve(id: "id")
 <dl>
 <dd>
 
-Update, freeze, or cancel a card. Updating the card's name, billing address, or limits requires both `payout:account:update` and `company:balance:read`; a card's assigned holder may update their own card's pin and frozen state with any user token.
+Updates, freezes, or cancels a card. Updating the card's name, billing address, or limits requires both `payout:account:update` and `company:balance:read`; a card's assigned holder may update their own card's pin and frozen state with any user token.
 </dd>
 </dl>
 </dd>
@@ -11170,7 +11149,7 @@ client.cards.update(id: "id")
 <dl>
 <dd>
 
-Creates a future-dated card cashback rule funded by the authenticated platform account. Requires payout:transfer_funds. Merchant name and MCC are optional. Every supplied merchant filter must match. When both are omitted or null, scoped_account_id is required and all eligible transactions for that account match. Optionally limit the rule to one direct connected account. The funding account is derived from the credential and cannot be supplied. Creation does not transfer funds. Supports Idempotency-Key for safe retries.
+Creates a future-dated card cashback rule for your direct connected accounts, funded by the authenticated platform account. Creating a rule does not transfer funds; pay cashback out with `POST /cashback_rules/payout`. Requires `payout:transfer_funds`. Supports `Idempotency-Key` for safe retries.
 </dd>
 </dl>
 </dd>
@@ -11243,7 +11222,7 @@ client.cashback_rules.create(
 <dl>
 <dd>
 
-**scoped_account_id:** `String` — Account ID prefixed biz_ belonging to a direct connected account. Required when both merchant filters are omitted or null. Otherwise, omit or set null to designate all direct connected accounts.
+**scoped_account_id:** `String` — Account ID, prefixed `biz_`, of one direct connected account to limit the rule to. Required when both merchant filters are omitted or `null`, in which case the rule matches all eligible transactions for that account. Otherwise, omit or set `null` to designate all direct connected accounts.
     
 </dd>
 </dl>
@@ -11283,7 +11262,7 @@ client.cashback_rules.create(
 <dl>
 <dd>
 
-Lists all cashback rules funded by the authenticated platform account. Includes scheduled, expired, and discarded rules. Requires payout:transfer:read. Account-scoped credentials are required; there is no caller-supplied funding-account filter.
+Lists the cashback rules funded by the authenticated platform account, including scheduled, expired, and discarded rules. Requires an account-scoped credential with `payout:transfer:read`.
 </dd>
 </dl>
 </dd>
@@ -11385,7 +11364,7 @@ client.cashback_rules.list
 <dl>
 <dd>
 
-Distributes cashback on demand from the authenticated platform's available USD balance to its direct connected accounts. Requires payout:transfer_funds. Optional filters combine; an empty body includes all eligible transactions. Only completed, unpaid transactions created before this request are considered. The latest matching rule wins; its funding account must be the authenticated platform. Amounts are calculated when processed. Returns status `processing` and echoes supplied filters when background processing is queued. Status `failed` with HTTP 200 means the queue rejected the request. This is not a payment confirmation. Failed transaction jobs retry automatically; insufficient funds requires adding USD to the funding wallet. Supports Idempotency-Key, and overlapping requests cannot pay the same card transaction twice.
+Pays out cashback on demand from the authenticated platform's available USD balance to its direct connected accounts. Covers completed, unpaid card transactions created before the request, each under its latest matching rule, which must be funded by the authenticated platform. Filters combine, and an empty body includes every eligible transaction. Payouts process in the background and amounts are calculated then, so the response confirms queuing, not payment. If a payout fails for insufficient funds, add USD to the platform's balance. Requires `payout:transfer_funds`. Supports `Idempotency-Key`, and overlapping requests cannot pay the same card transaction twice.
 </dd>
 </dl>
 </dd>
@@ -11463,7 +11442,7 @@ client.cashback_rules.payout
 <dl>
 <dd>
 
-Updates a cashback rule funded by the authenticated platform account. Requires payout:transfer_funds. Only merchant_name, merchant_category_code, description, and expires_at can change; starts_at, rate_bps, funding_account_id, and scoped_account_id are immutable. Omitted fields stay unchanged. Scheduled, active, and expired rules can be updated; discarded rules cannot. Updating a rule does not transfer funds.
+Updates the merchant filters, description, or expiration of a cashback rule funded by the authenticated platform account; its start, rate, and accounts can't change. Omitted fields stay unchanged. Scheduled, active, and expired rules can be updated, but discarded rules can't. Updating a rule does not transfer funds. Requires `payout:transfer_funds`.
 </dd>
 </dl>
 </dd>
@@ -11558,7 +11537,7 @@ client.cashback_rules.update(id: "id")
 <dl>
 <dd>
 
-Returns a paginated list of chat channels within a specific company, with optional filtering by product.
+Lists the chat channels in an account.
 
 Required permissions:
  - `chat:read`
@@ -11733,7 +11712,7 @@ client.chat_channels.retrieve(id: "id")
 <dl>
 <dd>
 
-Update moderation settings for a chat channel, such as who can post, banned words, and media restrictions.
+Updates a chat channel's moderation settings, such as who can post, banned words, and media restrictions.
 
 Required permissions:
  - `chat:moderate`
@@ -11965,7 +11944,7 @@ client.checkout_configurations.list(account_id: "account_id")
 <dl>
 <dd>
 
-Creates a reusable checkout configuration for an existing or inline variant.
+Creates a reusable checkout configuration for an existing or inline variant. Send customers to its `purchase_url` to check out.
 </dd>
 </dl>
 </dd>
@@ -12227,7 +12206,7 @@ client.checkout_configurations.delete(id: "id")
 <dl>
 <dd>
 
-Retrieves a funded claim link. IDs require `airdrop_link:basic:read` on the funding account, or the personal account's owner. Claim codes allow unauthenticated previews of the sender, amount, expiry, and claim availability. Treat codes as secrets: anyone holding one can claim after signing in. By ID, the code and URL require `airdrop_link:manage` on the funding company or `payout:withdraw_funds` on the personal account; read-only credentials receive null values.
+Retrieves a funded claim link by ID or by its public claim code. By ID, the caller needs `airdrop_link:basic:read` on the funding account, or must own the funding personal account; `code` and `claim_url` are `null` without `airdrop_link:manage` on the funding account or `payout:withdraw_funds` on the personal account. A claim code previews the sender, amount, expiry, and claim availability without authentication. Treat codes as secrets: anyone holding one can claim after signing in.
 </dd>
 </dl>
 </dd>
@@ -12289,7 +12268,7 @@ client.claim_links.retrieve(id: "id")
 <dl>
 <dd>
 
-Claims a funded link into the authenticated user's personal balance and returns the updated link. Requires a signed-in user and the public claim code; company API keys cannot claim on a recipient's behalf. Each user can claim a link once. Reuse the same Idempotency-Key when retrying the same request. On-chain claims wait for the existing transfer workflow and may take several minutes.
+Claims a funded link into the authenticated user's personal balance and returns the updated link. Requires a signed-in user and the public claim code; account API keys cannot claim on a recipient's behalf. Each user can claim a link once. Reuse the same `Idempotency-Key` when retrying the same request. On-chain claims may take several minutes to complete.
 </dd>
 </dl>
 </dd>
@@ -12352,7 +12331,7 @@ client.claim_links.claim(id: "id")
 <dl>
 <dd>
 
-Returns a paginated list of token transactions for a user or company, depending on the authenticated actor, with optional filtering by user and transaction type.
+Lists an account's token transactions, newest first.
 
 Required permissions:
  - `company_token_transaction:read`
@@ -12472,7 +12451,7 @@ client.company_token_transactions.list(
 <dl>
 <dd>
 
-Create a token transaction to add, subtract, or transfer tokens for a member within a company.
+Creates a token transaction that adds, subtracts, or transfers tokens for a member of an account.
 
 Required permissions:
  - `company_token_transaction:create`
@@ -12539,7 +12518,7 @@ client.company_token_transactions.create
 <dl>
 <dd>
 
-Retrieves the details of an existing company token transaction.
+Retrieves a token transaction.
 
 Required permissions:
  - `company_token_transaction:read`
@@ -12607,7 +12586,7 @@ client.company_token_transactions.retrieve(id: "id")
 <dl>
 <dd>
 
-Retrieves a token's payment method and billing details — never the underlying payment credential. Public and rate-limited: the account_id query param must match the account the token was minted for. A bearer credential with payment:basic:read on that account also receives the collected billing address.
+Retrieves a confirmation token's payment method and billing details, never the underlying payment credential, to display what the buyer chose or check that the token is still usable. Requires no authentication and is rate-limited.
 </dd>
 </dl>
 </dd>
@@ -12648,7 +12627,7 @@ client.confirmation_tokens.retrieve(
 <dl>
 <dd>
 
-**account_id:** `String` — The account (biz_) the token was minted for.
+**account_id:** `String` — The account the token was minted for, prefixed `biz_`. It must match the token's account.
     
 </dd>
 </dl>
@@ -13062,7 +13041,7 @@ client.course_chapters.update(
 <dl>
 <dd>
 
-Returns a paginated list of lesson interactions, filtered by lesson, course, user, or completion status.
+Returns a paginated list of lesson interactions for a lesson or course. Callers without admin access to the course's experience see only their own interactions.
 
 Required permissions:
  - `courses:read`
@@ -14175,7 +14154,7 @@ client.course_students.retrieve(id: "id")
 <dl>
 <dd>
 
-Returns a paginated list of courses, filtered by either an experience or a company.
+Returns a paginated list of the courses in an experience or an account. `hidden` courses are included only for callers with `courses:update`.
 
 Required permissions:
  - `courses:read`
@@ -14409,7 +14388,7 @@ client.courses.create(
 <dl>
 <dd>
 
-Retrieves the details of an existing course.
+Retrieves the details of an existing course. A `hidden` course is returned only to callers with `courses:update`.
 
 Required permissions:
  - `courses:read`
@@ -14685,7 +14664,7 @@ client.courses.update(id: "cors_xxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Retrieve the deposit methods for an account, including crypto and bank transfer. Bitcoin deposits are converted by Relay directly to USDT on Plasma in the destination account's wallet. Crypto deposits require a $10 minimum.
+Returns the deposit methods for an account or user, including crypto addresses, bank transfer instructions, and, for a business, a hosted deposit page. Bitcoin deposits are converted to USDT on Plasma in the destination's wallet. Business destinations require no authentication.
 </dd>
 </dl>
 </dd>
@@ -15267,7 +15246,7 @@ client.disputes.retrieve(id: "id")
 <dl>
 <dd>
 
-Edits a dispute's evidence, while it is still editable. Sending it is a separate call. `evidence.documents`, when provided, replaces the full set of documents beyond the four fixed evidence slots — see its own description.
+Edits a dispute's evidence while it is still editable. When the evidence is ready, send it to the payment processor with `POST /disputes/:id/submit`.
 </dd>
 </dl>
 </dd>
@@ -15399,7 +15378,7 @@ client.disputes.submit(id: "id")
 <dl>
 <dd>
 
-Prefer `PATCH /disputes/{id}` with `evidence.documents` — it does the same replace alongside every other evidence field in one call. Replaces the full set of uploaded evidence documents on a dispute, beyond the four fixed evidence slots. Upload files through `POST /files` and reference them by `id`, or send the files as multipart file parts to upload and attach in one call. Send every document the packet should carry — up to 10, 10MB each and 25MB in total; an empty list removes them all. Accepted content types: application/pdf, application/json, image/jpeg, image/png, image/webp — any other type is rejected. Policy documents (`return_policy`, `shipping_policy`, `cancellation_policy`, `terms_of_service`) default from the account's own documents; uploading one here replaces the account copy for this dispute, and a `cancellation_policy` or `return_policy` upload also takes precedence over the matching fixed evidence slot.
+Replaces the full set of uploaded evidence documents on a dispute, beyond the four fixed evidence slots. Prefer `PATCH /disputes/:id` with `evidence.documents`, which does the same replace alongside every other evidence field in one call.
 </dd>
 </dl>
 </dd>
@@ -15442,7 +15421,7 @@ client.disputes.upload_evidence(
 <dl>
 <dd>
 
-**documents:** `Internal::Types::Array[Whop_sdk::Disputes::Types::UploadEvidenceDisputesRequestDocumentsItem]` — The full set of evidence documents the dispute should carry, beyond the four fixed evidence slots. Replaces all previously uploaded documents. Upload files through `POST /files` and reference them by `id`, or send the files as multipart file parts to upload and attach in one call. Policy documents (`return_policy`, `shipping_policy`, `cancellation_policy`, `terms_of_service`) default from the account's own documents; uploading one here replaces the account copy for this dispute, and a `cancellation_policy` or `return_policy` upload also takes precedence over the matching fixed evidence slot.
+**documents:** `Internal::Types::Array[Whop_sdk::Disputes::Types::UploadEvidenceDisputesRequestDocumentsItem]` — The full set of evidence documents the dispute should carry, beyond the four fixed evidence slots. Replaces all previously uploaded documents; an empty list removes them all. Send up to 10, 10MB each and 25MB in total. Accepted content types: application/pdf, application/json, image/jpeg, image/png, image/webp — any other type is rejected. Upload files through `POST /files` and reference them by `id`, or send the files as multipart file parts to upload and attach in one call. Policy documents (`return_policy`, `shipping_policy`, `cancellation_policy`, `terms_of_service`) default from the account's own documents; uploading one here replaces the account copy for this dispute, and a `cancellation_policy` or `return_policy` upload also takes precedence over the matching fixed evidence slot.
     
 </dd>
 </dl>
@@ -15475,7 +15454,7 @@ client.disputes.upload_evidence(
 <dl>
 <dd>
 
-Returns a paginated list of DM channels for the currently authenticated user, sorted by most recently active.
+Lists the authenticated user's DM channels, most recently active first.
 
 Required permissions:
  - `dms:read`
@@ -15576,7 +15555,7 @@ client.dm_channels.list(
 <dl>
 <dd>
 
-Create a new DM channel between two or more users, optionally scoped to a specific company. Returns the existing channel if one already exists.
+Creates a DM channel between two or more users, optionally scoped to an account. Returns the existing channel if one already exists.
 
 Required permissions:
  - `dms:channel:manage`
@@ -15731,7 +15710,7 @@ client.dm_channels.retrieve(id: "id")
 <dl>
 <dd>
 
-Permanently delete a DM channel and all of its messages. Only an admin of the channel can perform this action.
+Permanently deletes a DM channel and all of its messages. Only a channel admin can delete it.
 
 Required permissions (one of):
  - `dms:channel:manage`
@@ -15797,7 +15776,7 @@ client.dm_channels.delete(id: "id")
 <dl>
 <dd>
 
-Update the settings of an existing DM channel, such as its display name. Only an admin of the channel can perform this action.
+Updates a DM channel's settings, such as its display name. Only a channel admin can update it.
 
 Required permissions (one of):
  - `dms:channel:manage`
@@ -16322,7 +16301,7 @@ client.domains.list(tlds: ["com"])
 <dl>
 <dd>
 
-**order:** `Whop_sdk::Domains::Types::ListDomainsRequestOrder` — Field to sort by.
+**order:** `Whop_sdk::Domains::Types::ListDomainsRequestOrder` — Field to sort by. Domains with the same value keep their creation order in the same direction.
     
 </dd>
 </dl>
@@ -16426,6 +16405,22 @@ client.domains.list(tlds: ["com"])
 <dl>
 <dd>
 
+**apple_pay:** `Whop_sdk::Domains::Types::ListDomainsRequestApplePay` — Only domains with apple_pay in this state, such as `ready`, or `any` for every domain that has apple_pay.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**pixel:** `Whop_sdk::Domains::Types::ListDomainsRequestPixel` — Only domains with pixel in this state, such as `ready`, or `any` for every domain that has pixel.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **request_options:** `Whop_sdk::Domains::RequestOptions` 
     
 </dd>
@@ -16494,6 +16489,14 @@ client.domains.create(domain: "store.example.com")
 <dl>
 <dd>
 
+**apple_pay:** `Whop_sdk::Domains::Types::CreateDomainsRequestApplePay` — Accept Apple Pay at checkout on the domain. It needs no other capability. Whop registers the domain with Apple: it stays `pending` until Apple answers, then turns `ready`, or `action_required` when Apple couldn't fetch the domain association file. Serve the file, then check the domain to register it again. Pass `null` to turn Apple Pay off: Whop removes the domain from Apple, and the domain stays, like releasing any other capability.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **domain:** `String` — Bare hostname, such as example.com or checkout.example.com. A bought domain must be a root domain. Wildcards, paths, schemes, and ports are not accepted.
     
 </dd>
@@ -16510,6 +16513,14 @@ client.domains.create(domain: "store.example.com")
 <dl>
 <dd>
 
+**pixel:** `Whop_sdk::Domains::Types::CreateDomainsRequestPixel` — Track page views on the domain with the Whop pixel. It needs no other capability: it stays `pending` until the pixel records a page view, and turns `action_required` if it goes 7 days without one. Pass `null` to stop tracking.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **registration:** `Whop_sdk::Domains::Types::CreateDomainsRequestRegistration` — Buy the domain through Whop, renew it every year, and let Whop run its DNS. Pass `null` to release an unpaid or failed purchase.
     
 </dd>
@@ -16722,6 +16733,14 @@ client.domains.update(id: "id")
 <dl>
 <dd>
 
+**apple_pay:** `Whop_sdk::Domains::Types::UpdateDomainsRequestApplePay` — Accept Apple Pay at checkout on the domain. It needs no other capability. Whop registers the domain with Apple: it stays `pending` until Apple answers, then turns `ready`, or `action_required` when Apple couldn't fetch the domain association file. Serve the file, then check the domain to register it again. Pass `null` to turn Apple Pay off: Whop removes the domain from Apple, and the domain stays, like releasing any other capability.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **metadata:** `Internal::Types::Hash[String, String]` — Replacement custom string keys and values.
     
 </dd>
@@ -16730,6 +16749,14 @@ client.domains.update(id: "id")
 <dl>
 <dd>
 
+**pixel:** `Whop_sdk::Domains::Types::UpdateDomainsRequestPixel` — Track page views on the domain with the Whop pixel. It needs no other capability: it stays `pending` until the pixel records a page view, and turns `action_required` if it goes 7 days without one. Pass `null` to stop tracking.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **registration:** `Whop_sdk::Domains::Types::UpdateDomainsRequestRegistration` — Buy the domain through Whop, renew it every year, and let Whop run its DNS. Pass `null` to release an unpaid or failed purchase.
     
 </dd>
@@ -16841,7 +16868,7 @@ client.domains.check(id: "id")
 <dl>
 <dd>
 
-Lists an account's recommendations and generation requests, newest first by default. For callers with company:update permission, listing queues generation when no recommendations are ready or in progress, with a ten-minute cooldown after an unsuccessful request; unsuccessful requests are not listed. Without an account, signed-out visitors receive a business-setup template and eligible users receive their saved setup recommendation. With `has_run` and no account, users receive the recommendations run on every account they can read that has Economic Intelligence. An account's executed recommendations and runs stay listed after Economic Intelligence turns off. New recommendations are offered only while it is on. Visitor countries, page views, ad impressions and clicks, and payment volume for a time range come from `GET /stats/time_series/{metric}`.
+Lists an account's recommendations and generation requests, newest first by default. When no recommendations are ready or in progress and you have `company:update` permission, listing queues generation, with a ten-minute cooldown after an unsuccessful request; unsuccessful requests are not listed. An account's executed recommendations and runs stay listed after Economic Intelligence turns off, but new recommendations are offered only while it is on. For visitor countries, page views, ad impressions and clicks, or payment volume over a time range, use `GET /stats/time_series/:metric`.
 </dd>
 </dl>
 </dd>
@@ -16871,7 +16898,7 @@ client.economic_intelligence.list
 <dl>
 <dd>
 
-**account_id:** `String` — Account ID, prefixed `biz_`. Defaults to the API key's own account; omit for personal onboarding.
+**account_id:** `String` — Account ID, prefixed `biz_`. Defaults to the API key's own account; omit for personal onboarding, where signed-out visitors receive a business-setup template and eligible users receive their saved setup recommendation.
     
 </dd>
 </dl>
@@ -17102,7 +17129,7 @@ client.economic_intelligence.update(id: "id")
 <dl>
 <dd>
 
-Lists identity-linked events, most recent first by default. Pass identifier for one person's journey, or omit it to list events for an account within an explicit time range. Pass direction=asc to read a journey forwards from where it starts. Events are shaped like the POST /events intake: attribution in context, identity in user.
+Lists identity-linked events, most recent first by default. Pass `identifier` for one person's journey, or omit it to list an account's events within a time range. Events have the same shape as the `POST /events` intake: attribution in `context`, identity in `user`.
 </dd>
 </dl>
 </dd>
@@ -17308,7 +17335,7 @@ client.events.list
 <dl>
 <dd>
 
-Tracks a conversion or engagement event for an account.
+Tracks a conversion or engagement event for an account, such as a lead or a sign-up, so it can be attributed to the ads and links that drove it. Send server-side events with an API key that has `event:create`; the browser pixel calls this without authentication.
 </dd>
 </dl>
 </dd>
@@ -17529,7 +17556,7 @@ Use a standard event (lead, submit_application, contact, complete_registration,
 <dl>
 <dd>
 
-Returns a fully anonymized feed of recent platform-wide money movement, most recent first: purchases, affiliate commissions, card and ad spend, app revenue, off-platform sales, wallet deposits, card loads, claimed drops, transfers between accounts, and referral bonuses. Items carry only a `type`, the underlying event name, a USD amount, a coarse location under `user`, and a timestamp coarsened to the start of the minute; missing fields are omitted, not nulled. The payload is identical for every caller; no auth is required.
+Returns a fully anonymized feed of recent money movement across Whop, most recent first, such as purchases, card spend, and transfers between accounts. Each item carries only its `type`, a USD amount, a coarse location, and a timestamp coarsened to the minute. The payload is identical for every caller and requires no authentication.
 </dd>
 </dl>
 </dd>
@@ -17615,7 +17642,7 @@ client.events.pulse
 <dl>
 <dd>
 
-Checks whether the Whop pixel is installed for an account. Recent pixel events count as proof on their own, so an account that has sent data lately comes back installed without a `url`. Pass a `url` and events from that page settle it; conversion events are also read across the hostname because they commonly fire on a later confirmation page. If the requested page hasn't sent any events lately, it is fetched and read for the pixel and conversion events wired on it. `installed` is only true when the pixel was actually seen — in the account's events or in the page. `affiliate_tracking_detected` reports an affiliate tracking SDK found on the page. Supported platforms: Everflow.
+Checks whether the Whop pixel is installed for an account, or on one page when you pass a `url`. Use it before launching an ad to confirm its destination is tracked, or in a setup flow to tell a merchant whether their install is live.
 </dd>
 </dl>
 </dd>
@@ -17653,7 +17680,7 @@ client.events.validate_pixel
 <dl>
 <dd>
 
-**url:** `String` — A page to read for the pixel, e.g. an ad destination. Omit it to check the account from its events alone.
+**url:** `String` — A page to check for the pixel, such as an ad destination. Events from that page settle the answer; if it hasn't sent any lately, it is fetched and its source read for the pixel and the conversion events wired on it. Omit it to check the account from its events alone.
     
 </dd>
 </dl>
@@ -17686,7 +17713,7 @@ client.events.validate_pixel
 <dl>
 <dd>
 
-Returns a paginated list of experiences belonging to a company, with optional filtering by product and app.
+Lists the experiences in an account, optionally filtered to those attached to one product or powered by one app.
 </dd>
 </dl>
 </dd>
@@ -17820,6 +17847,8 @@ client.experiences.list(
 <dl>
 <dd>
 
+Creates an experience for an account, powered by an app such as courses, forums, or chat. Attach it to a product with `POST /experiences/:id/attach` to give that product's customers access.
+
 Required permissions:
  - `experience:create`
 </dd>
@@ -17996,6 +18025,8 @@ client.experiences.retrieve(id: "exp_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
+Deletes an experience and detaches it from every product, removing customer access to it. Returns `true` on success.
+
 Required permissions:
  - `experience:delete`
 </dd>
@@ -18059,6 +18090,8 @@ client.experiences.delete(id: "exp_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
+Updates an experience's name, logo, visibility, or notification setting, or moves it to another section or position.
+
 Required permissions:
  - `experience:update`
 </dd>
@@ -18178,7 +18211,7 @@ client.experiences.update(id: "exp_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Attach an experience to a product, making it accessible to the product's customers.
+Attaches an experience to a product, giving the product's customers access to it.
 
 Required permissions:
  - `experience:attach`
@@ -18254,7 +18287,7 @@ client.experiences.attach(
 <dl>
 <dd>
 
-Detach an experience from a product, removing customer access to it through that product.
+Detaches an experience from a product, removing customer access to it through that product.
 
 Required permissions:
  - `experience:detach`
@@ -18330,10 +18363,7 @@ client.experiences.detach(
 <dl>
 <dd>
 
-Duplicates an existing experience. The name will be copied, unless provided. The new experience will be attached to the same products as the original experience.
-If duplicating a Forum or Chat experience, the new experience will have the same settings as the original experience, e.g. who can post, who can comment, etc.
-No content, e.g. posts, messages, lessons from within the original experience will be copied.
-
+Duplicates an experience and attaches the copy to the same products as the original. Forum and chat copies keep the original's settings, such as who can post or comment. No content, such as posts, messages, or lessons, is copied.
 
 Required permissions:
  - `experience:create`
@@ -18407,7 +18437,7 @@ client.experiences.duplicate(id: "exp_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Lists experiments for one account with experiment:read permission.
+Lists the experiments and feature flags owned by an account. Requires `experiment:read` on the account.
 </dd>
 </dl>
 </dd>
@@ -18533,7 +18563,7 @@ client.experiments.list
 <dl>
 <dd>
 
-Creates a draft experiment for the specified account.
+Creates an experiment or feature flag in `draft` status for an account. Nothing is served until you activate it with `POST /experiments/:id/activate`. Requires `experiment:manage` on the account.
 </dd>
 </dl>
 </dd>
@@ -18670,15 +18700,7 @@ client.experiments.create(
 <dl>
 <dd>
 
-Evaluates and records an exposure without requiring authentication. When credentials resolve, their authentication method, API key ID, and signed-in user ID are recorded on the exposure event. Pass subject for bucketing identity and account_id for experiment ownership.
-
-Pass `flag_key` to check a single flag, or omit it to fetch active flags in the account and related resource scope.
-
-Assignments use exactly the configured `bucket_by`: `subject[user_id]`, `subject[account_id]`, or `subject[anonymous_id]`. Missing the required identity fails single evaluation and omits the experiment from batch evaluation. Subjects outside all treatment ranges receive control.
-
-Pass `subject[account_id]` to enable account-level targeting rules. Pass `properties` as a JSON object to supply the values that `property` targeting conditions match against.
-
-Pass `log_exposure=false` to read an assignment without recording an exposure, for a client that caches assignments up front and records the exposure when the arm is actually rendered. Omitted records the exposure, so pinned callers are unchanged.
+Evaluates experiments and feature flags for a subject and records an exposure. Pass `flag_key` to evaluate one flag, or omit it to evaluate every active flag in the account and related resource scope. Requires no authentication; when a credential resolves, its authentication method, API key ID, and signed-in user ID are recorded on the exposure event.
 </dd>
 </dl>
 </dd>
@@ -18708,7 +18730,7 @@ client.experiments.exposures
 <dl>
 <dd>
 
-**subject:** `Whop_sdk::Types::ExposuresExperimentsRequestSubject` — Bucketing subject: the user, account, or anonymous ID the experiment's `bucket_by` assigns on. Ownership is the top-level account_id.
+**subject:** `Whop_sdk::Types::ExposuresExperimentsRequestSubject` — Bucketing subject: the user, account, or anonymous ID the experiment's `bucket_by` assigns on. Only the identity matching `bucket_by` is used; when it is missing, evaluating a single flag fails and a batch omits that experiment. Subjects outside every treatment range receive `control`. `subject[account_id]` also enables account-level targeting rules. Experiment ownership comes from the top-level `account_id`.
     
 </dd>
 </dl>
@@ -18748,7 +18770,7 @@ client.experiments.exposures
 <dl>
 <dd>
 
-**log_exposure:** `Internal::Types::Boolean` — Set false to evaluate without recording an exposure. Omitted records it.
+**log_exposure:** `Internal::Types::Boolean` — Set `false` to read an assignment without recording an exposure, such as when a client caches assignments up front and records the exposure when the arm is rendered. Omitted records the exposure.
     
 </dd>
 </dl>
@@ -18780,7 +18802,7 @@ client.experiments.exposures
 <dl>
 <dd>
 
-Retrieves a single experiment or feature flag by its `expt_` id or flag_key handle. Requires the corresponding experiment permission on the owning account.
+Retrieves an experiment or feature flag by its `expt_` ID or `flag_key` handle. Requires `experiment:read` on the owning account.
 </dd>
 </dl>
 </dd>
@@ -18850,7 +18872,7 @@ client.experiments.retrieve(id: "id")
 <dl>
 <dd>
 
-Updates the targeting rules, treatment allocation, metrics, or hypothesis of an existing experiment or feature flag. Weights and metrics can only grow, so enrolled users never change arms and an existing metric is never dropped. Lifecycle moves through the transition endpoints (`activate`, `pause`, `end`), never through this update. Requires the corresponding experiment permission on the owning account.
+Updates the targeting rules, treatment allocation, or hypothesis of an existing experiment or feature flag. To change its lifecycle, use the `activate`, `pause`, and `end` endpoints instead. Requires `experiment:manage` on the owning account.
 </dd>
 </dl>
 </dd>
@@ -18960,7 +18982,7 @@ client.experiments.update(id: "id")
 <dl>
 <dd>
 
-Starts (or resumes) an experiment or feature flag so evaluation begins serving it. Activating a draft stamps `started_at`; resuming a paused experiment keeps the original start. Only drafts and paused experiments can be activated. Requires the corresponding experiment permission on the owning account.
+Starts (or resumes) an experiment or feature flag so evaluation begins serving it. Activating a draft stamps `started_at`; resuming a paused experiment keeps the original start. Only drafts and paused experiments can be activated. Requires `experiment:manage` on the owning account.
 </dd>
 </dl>
 </dd>
@@ -19038,7 +19060,7 @@ client.experiments.activate(id: "id")
 <dl>
 <dd>
 
-Concludes the experiment and records required `findings`. Pass `winning_arm` to serve the winning treatment to everyone; omit it when control won. Ended experiments cannot restart, but may be ended again to correct the winner. Requires experiment:manage on the account.
+Concludes the experiment and records required `findings`. Pass `winning_arm` to serve the winning treatment to everyone; omit it when control won. Ended experiments cannot restart, but may be ended again to correct the winner. Requires `experiment:manage` on the owning account.
 </dd>
 </dl>
 </dd>
@@ -19127,7 +19149,7 @@ client.experiments.end_(
 <dl>
 <dd>
 
-Pauses an active experiment or feature flag: evaluation stops serving it and exposures stop flowing. Assignments are keyed on stable identity, so users return to their original arm when the experiment resumes. Requires the corresponding experiment permission on the owning account.
+Pauses an active experiment or feature flag: evaluation stops serving it and exposures stop flowing. Assignments are keyed on stable identity, so users return to their original arm when the experiment resumes. Requires `experiment:manage` on the owning account.
 </dd>
 </dl>
 </dd>
@@ -19308,7 +19330,7 @@ client.exports.list
 <dl>
 <dd>
 
-Starts an asynchronous export of a resource for an account. Returns the export in `pending`; poll `GET /exports/{id}` until `download_url` is set.
+Starts an asynchronous export of a resource for an account. Returns the export in `pending`; poll `GET /exports/:id` until `download_url` is set.
 </dd>
 </dl>
 </dd>
@@ -19685,7 +19707,7 @@ client.external_accounts.create(platform: "facebook")
 <dl>
 <dd>
 
-Starts an OAuth connection flow and returns an authorize_url where the user can connect an external account. LinkedIn supports personal profiles only, with scopes omitted. TikTok connects the authenticated user’s profile when scopes are omitted or company advertising assets with advertise. Meta Business and Snapchat support advertising connections only and require advertise. Personal profile connections must be completed in a browser signed in as the initiating Whop user.
+Starts an OAuth connection flow and returns an `authorize_url` to send the user to, where they connect an external account. Personal profile connections must be completed in a browser signed in as the Whop user who started the flow.
 </dd>
 </dl>
 </dd>
@@ -19923,7 +19945,7 @@ client.external_accounts.refresh(id: "id")
 <dl>
 <dd>
 
-Returns a paginated list of fee markups configured for a company. If the company is a platform account, returns the platform default markups.
+Lists the fee markups configured for an account. For a platform account, returns the platform's default markups.
 
 Required permissions:
  - `company:update_child_fees`
@@ -20024,7 +20046,7 @@ client.fee_markups.list(
 <dl>
 <dd>
 
-Create or update a fee markup for a company. If a markup for the specified fee type already exists, it will be updated with the new values.
+Creates or updates an account's markup for one fee type. If the account already has a markup for that `fee_type`, it is updated with the new values.
 
 Required permissions:
  - `company:update_child_fees`
@@ -20132,7 +20154,7 @@ client.fee_markups.create(
 <dl>
 <dd>
 
-Delete a fee markup configuration for a company. This removes the custom fee override and reverts to the parent company's default fees.
+Deletes a fee markup, removing the custom fee override so the account reverts to its parent account's default fees.
 
 Required permissions:
  - `company:update_child_fees`
@@ -20198,7 +20220,7 @@ client.fee_markups.delete(id: "id")
 <dl>
 <dd>
 
-Submits an issue or an unanswered question to Whop for review, recorded under the authenticated user, account, or app. Returns a receipt once the submission is accepted; processing is asynchronous and no reply is sent. Accepts user, account, and app credentials.
+Submits an issue or an unanswered question to Whop for review, recorded under the authenticated user, account, or app. Returns a receipt once the submission is accepted; processing is asynchronous and no reply is sent.
 </dd>
 </dl>
 </dd>
@@ -20280,7 +20302,7 @@ client.feedback_submissions.create(
 <dl>
 <dd>
 
-Returns the files with the given IDs, newest first — fetch a batch in one request instead of retrieving each file individually. Only files you created are returned; IDs that do not exist, or that another credential created, are omitted. A request for up to 100 IDs answers in a single page by default; a larger batch pages at up to 100 files per response — follow `page_info` with the same `file_ids` to walk the rest.
+Returns the files with the given IDs, newest first — fetch a batch in one request instead of retrieving each file individually. Only files you created are returned; IDs that do not exist, or that another credential created, are omitted. For a batch larger than one page, follow `page_info` with the same `file_ids` to walk the rest.
 </dd>
 </dl>
 </dd>
@@ -21126,7 +21148,7 @@ client.forum_posts.list(
 <dl>
 <dd>
 
-Create a new forum post or comment within an experience. Supports text content, attachments, polls, paywalling, and pinning. Pass experience_id 'public' with an account_id to post to an account's public forum.
+Create a new forum post or comment within an experience. Supports text content, attachments, polls, paywalling, and pinning.
 
 Required permissions:
  - `forum:post:create`
@@ -21455,7 +21477,7 @@ client.forum_posts.update(id: "id")
 <dl>
 <dd>
 
-Returns a paginated list of forums within a specific company, with optional filtering by product.
+Returns a paginated list of forums for an account, with optional filtering by product.
 
 Required permissions:
  - `forum:read`
@@ -21736,7 +21758,7 @@ client.forums.update(id: "id")
 <dl>
 <dd>
 
-Returns a paginated list of identity profiles. When account_id is provided, lists IPs currently linked to that account's ledger. When omitted, lists IPs linked to any ledger the actor can read (including child accounts under a parent).
+Lists the identity profiles currently linked to an account, or to every account you can read when `account_id` is omitted.
 
 Required permissions:
  - `identity:read`
@@ -21821,7 +21843,7 @@ client.identity_profiles.list_identity_profile(
 <dl>
 <dd>
 
-**account_id:** `String` — The unique identifier of the company to filter to. When omitted, returns IPs across all ledgers the actor can read.
+**account_id:** `String` — Account to list identity profiles for, prefixed `biz_`. Omit to list profiles across every account you can read, including child accounts under a parent and, with a user credential, your own user.
     
 </dd>
 </dl>
@@ -21918,7 +21940,7 @@ client.identity_profiles.retrieve_identity_profile(id: "idpf_xxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Unlinks an IdentityProfile from a LedgerAccount (flips the matching link to is_current=false).
+Unlinks an identity profile from the account or user that owns `ledger_account_id`. Requires `identity:write` on that account or user.
 </dd>
 </dl>
 </dd>
@@ -22093,7 +22115,7 @@ client.identity_profiles.list_verifications_identity_profile(
 <dl>
 <dd>
 
-Returns a paginated list of invoices for a company, with optional filtering by product, status, collection method, and creation date.
+Returns a paginated list of invoices for an account, with optional filtering by product, status, collection method, and creation date.
 
 Required permissions:
  - `invoice:basic:read`
@@ -22901,7 +22923,7 @@ client.invoices.void(id: "inv_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Returns a paginated list of leads for a company, with optional filtering by product and creation date.
+Lists an account's leads, newest first.
 
 Required permissions:
  - `lead:basic:read`
@@ -23031,7 +23053,7 @@ client.leads.list(
 <dl>
 <dd>
 
-Record a new lead for a company, capturing a potential customer's interest in a specific product.
+Records a lead: a potential customer's interest in an account or one of its products.
 
 Required permissions:
  - `lead:manage`
@@ -23199,7 +23221,7 @@ client.leads.retrieve(id: "lead_xxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Update the metadata or referrer information on an existing lead record.
+Updates a lead's `metadata` or `referrer`.
 
 Required permissions:
  - `lead:manage`
@@ -23534,7 +23556,12 @@ Lists the members of an account. A member is one buyer's relationship with the a
 <dd>
 
 ```ruby
-client.members.list(user_ids: ["user_xxxxxxxxxxxxxx"])
+client.members.list(
+  user_ids: ["user_xxxxxxxxxxxxxx"],
+  product_ids: ["prod_xxxxxxxxxxxxx"],
+  plan_ids: ["plan_xxxxxxxxxxxxx"],
+  promo_code_ids: ["promo_xxxxxxxxxxxx"]
+)
 ```
 </dd>
 </dl>
@@ -23581,6 +23608,46 @@ client.members.list(user_ids: ["user_xxxxxxxxxxxxxx"])
 <dl>
 <dd>
 
+**most_recent_actions:** `Whop_sdk::Members::Types::ListMembersRequestMostRecentActionsItem` — Only return members whose `most_recent_action` is one of these values.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**membership_status:** `Whop_sdk::Members::Types::ListMembersRequestMembershipStatus` — `active` returns members holding at least one membership that currently grants access; `inactive` returns members holding at least one membership that does not. Combined with `product_ids`, `plan_ids`, or `promo_code_ids`, one membership must match all of them.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**product_ids:** `String` — Only return members holding a membership to one of these products, prefixed `prod_`. Unknown IDs match nothing.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**plan_ids:** `String` — Only return members holding a membership on one of these plans, prefixed `plan_`. Unknown IDs match nothing.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**promo_code_ids:** `String` — Only return members holding a membership bought with one of these promo codes, prefixed `promo_`. Unknown IDs match nothing.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **query:** `String` — Search members by name or username. An exact email address also matches when the credential holds the member:email:read scope.
     
 </dd>
@@ -23605,7 +23672,7 @@ client.members.list(user_ids: ["user_xxxxxxxxxxxxxx"])
 <dl>
 <dd>
 
-**order:** `Whop_sdk::Members::Types::ListMembersRequestOrder` — Sort field.
+**order:** `Whop_sdk::Members::Types::ListMembersRequestOrder` — Sort field. `most_recent_action_at` places members without one first when ascending and last when descending.
     
 </dd>
 </dl>
@@ -23755,7 +23822,11 @@ Lists every membership the caller can read: an account API key its account's; a
 <dd>
 
 ```ruby
-client.memberships.list
+client.memberships.list(
+  product_ids: ["prod_xxxxxxxxxxxxx"],
+  plan_ids: ["plan_xxxxxxxxxxxxx"],
+  promo_code_ids: ["promo_xxxxxxxxxxxxxx"]
+)
 ```
 </dd>
 </dl>
@@ -23786,7 +23857,7 @@ client.memberships.list
 <dl>
 <dd>
 
-**status:** `Whop_sdk::Memberships::Types::ListMembershipsRequestStatus` — Filter by billing state. `canceling` matches active memberships set to cancel at period end; `paused` matches memberships with payment collection paused.
+**member_id:** `String` — Narrow to one member's memberships (`mber_` tag), including memberships bought by another business. A member outside the caller's visible set returns an empty list.
     
 </dd>
 </dl>
@@ -23794,7 +23865,7 @@ client.memberships.list
 <dl>
 <dd>
 
-**product_id:** `String` — Filter to memberships of this product (`prod_` tag). Repeat as product_ids[] for several.
+**status:** `Whop_sdk::Memberships::Types::ListMembershipsRequestStatus` — Filter by billing state. `trialing`, `active`, `past_due`, `completed`, `canceled`, and `expired` match the membership's `status`; `active`, `trialing`, and `past_due` exclude memberships set to cancel at period end. The other values are derived buckets that never appear as a `status`: `canceling` matches memberships set to cancel at period end; `paused` matches memberships with payment collection paused; `expiring` matches one-time purchases that have not yet expired; `one_time` matches one-time purchases that never expire; `unclaimed` matches memberships with no buyer user, including memberships bought by another business; `banned` matches memberships whose buyer is banned from the account.
     
 </dd>
 </dl>
@@ -23802,7 +23873,7 @@ client.memberships.list
 <dl>
 <dd>
 
-**plan_id:** `String` — Filter to memberships of this variant (`plan_` tag). Repeat as plan_ids[] for several.
+**statuses:** `Whop_sdk::Memberships::Types::ListMembershipsRequestStatusesItem` — Filter to memberships matching any of these billing states, with the same meanings as `status`. Repeat the parameter to pass several. Combined with `status` when both are sent.
     
 </dd>
 </dl>
@@ -23810,7 +23881,7 @@ client.memberships.list
 <dl>
 <dd>
 
-**created_after:** `String` — Only memberships created after this ISO 8601 timestamp.
+**product_id:** `String` — Filter to memberships of this product (`prod_` tag).
     
 </dd>
 </dl>
@@ -23818,7 +23889,7 @@ client.memberships.list
 <dl>
 <dd>
 
-**created_before:** `String` — Only memberships created before this ISO 8601 timestamp.
+**product_ids:** `String` — Filter to memberships of any of these products, each prefixed `prod_`. Repeat the parameter to pass several.
     
 </dd>
 </dl>
@@ -23826,7 +23897,7 @@ client.memberships.list
 <dl>
 <dd>
 
-**order:** `Whop_sdk::Memberships::Types::ListMembershipsRequestOrder` — Sort field.
+**plan_id:** `String` — Filter to memberships of this variant (`plan_` tag).
     
 </dd>
 </dl>
@@ -23834,7 +23905,7 @@ client.memberships.list
 <dl>
 <dd>
 
-**direction:** `Whop_sdk::Memberships::Types::ListMembershipsRequestDirection` — Sort direction.
+**plan_ids:** `String` — Filter to memberships of any of these variants, each prefixed `plan_`. Repeat the parameter to pass several.
     
 </dd>
 </dl>
@@ -23842,7 +23913,7 @@ client.memberships.list
 <dl>
 <dd>
 
-**first:** `Integer` — Number of results to return from the start of the range.
+**promo_code_ids:** `String` — Filter to memberships discounted by any of these promo codes, each prefixed `promo_`. Repeat the parameter to pass several.
     
 </dd>
 </dl>
@@ -23850,7 +23921,7 @@ client.memberships.list
 <dl>
 <dd>
 
-**after:** `String` — Return results after this cursor. Use `page_info.end_cursor` from the previous response to fetch the next page.
+**created_after:** `String` — Only memberships created after this ISO 8601 timestamp.
     
 </dd>
 </dl>
@@ -23858,7 +23929,7 @@ client.memberships.list
 <dl>
 <dd>
 
-**last:** `Integer` — Number of results to return from the end of the range.
+**created_before:** `String` — Only memberships created before this ISO 8601 timestamp.
     
 </dd>
 </dl>
@@ -23866,7 +23937,7 @@ client.memberships.list
 <dl>
 <dd>
 
-**before:** `String` — Return results before this cursor. Use `page_info.start_cursor` from the previous response to fetch the previous page.
+**order:** `Whop_sdk::Memberships::Types::ListMembershipsRequestOrder` — Sort field.
     
 </dd>
 </dl>
@@ -23874,64 +23945,39 @@ client.memberships.list
 <dl>
 <dd>
 
-**request_options:** `Whop_sdk::Memberships::RequestOptions` 
+**direction:** `Whop_sdk::Memberships::Types::ListMembershipsRequestDirection` — Sort direction.
     
 </dd>
 </dl>
-</dd>
-</dl>
-
 
-</dd>
-</dl>
-</details>
-
-<details><summary><code>client.memberships.<a href="/lib/whop_sdk/memberships/client.rb">invite</a>(request) -> Whop_sdk::Memberships::Types::InviteMembershipsResponse</code></summary>
 <dl>
 <dd>
 
-#### 📝 Description
-
-<dl>
-<dd>
+**first:** `Integer` — Number of results to return from the start of the range.
+    
+</dd>
+</dl>
 
 <dl>
 <dd>
 
-Sends an email inviting one recipient to join the account through a free variant. Identify the recipient by exactly one of `user_id` or `email`. The invitation is bound to that recipient; after signing in, accepting it immediately grants the membership without checkout. This Experimental endpoint is available only to accounts enabled for membership invitations.
-</dd>
-</dl>
+**after:** `String` — Return results after this cursor. Use `page_info.end_cursor` from the previous response to fetch the next page.
+    
 </dd>
 </dl>
 
-#### 🔌 Usage
-
-<dl>
-<dd>
-
 <dl>
 <dd>
 
-```ruby
-client.memberships.invite(
-  plan_id: "plan_xxxxxxxxxxxxxx",
-  user_id: "user_xxxxxxxxxxxxxx"
-)
-```
-</dd>
-</dl>
+**last:** `Integer` — Number of results to return from the end of the range.
+    
 </dd>
 </dl>
 
-#### ⚙️ Parameters
-
-<dl>
-<dd>
-
 <dl>
 <dd>
 
-**request:** `Whop_sdk::Memberships::Types::InviteMembershipsRequestBody` 
+**before:** `String` — Return results before this cursor. Use `page_info.start_cursor` from the previous response to fetch the previous page.
     
 </dd>
 </dl>
@@ -23951,7 +23997,7 @@ client.memberships.invite(
 </dl>
 </details>
 
-<details><summary><code>client.memberships.<a href="/lib/whop_sdk/memberships/client.rb">retrieve</a>(id:) -> Whop_sdk::Types::Membership</code></summary>
+<details><summary><code>client.memberships.<a href="/lib/whop_sdk/memberships/client.rb">invite</a>(request) -> Whop_sdk::Memberships::Types::InviteMembershipsResponse</code></summary>
 <dl>
 <dd>
 
@@ -23963,7 +24009,7 @@ client.memberships.invite(
 <dl>
 <dd>
 
-Retrieves a membership by ID or license key. Accessible to the account and to the membership's own user.
+Emails one recipient an invitation to a free variant's membership. The invitation is bound to that recipient; after signing in, accepting it immediately grants the membership without checkout. This Experimental endpoint is available only to accounts enabled for membership invitations.
 </dd>
 </dl>
 </dd>
@@ -23978,7 +24024,10 @@ Retrieves a membership by ID or license key. Accessible to the account and to th
 <dd>
 
 ```ruby
-client.memberships.retrieve(id: "id")
+client.memberships.invite(
+  plan_id: "plan_xxxxxxxxxxxxxx",
+  user_id: "user_xxxxxxxxxxxxxx"
+)
 ```
 </dd>
 </dl>
@@ -23993,7 +24042,7 @@ client.memberships.retrieve(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — Membership ID (`mem_` tag), or a software license key.
+**request:** `Whop_sdk::Memberships::Types::InviteMembershipsRequestBody` 
     
 </dd>
 </dl>
@@ -24013,7 +24062,7 @@ client.memberships.retrieve(id: "id")
 </dl>
 </details>
 
-<details><summary><code>client.memberships.<a href="/lib/whop_sdk/memberships/client.rb">update</a>(id:, request) -> Whop_sdk::Types::Membership</code></summary>
+<details><summary><code>client.memberships.<a href="/lib/whop_sdk/memberships/client.rb">retrieve</a>(id:) -> Whop_sdk::Types::Membership</code></summary>
 <dl>
 <dd>
 
@@ -24025,7 +24074,7 @@ client.memberships.retrieve(id: "id")
 <dl>
 <dd>
 
-Updates a membership: merge metadata key-value pairs, toggle `cancel_at_period_end` — `true` schedules the cancellation for the end of the current billing period, `false` reverses a pending one — or move future renewals to another of the customer's saved payment methods with `payment_method_id`, or set `billing_period_days` to change renewal cadence for an active, trialing, or past-due membership billed automatically by Whop. The current period end moves to the current period start plus the requested number of days, and future renewals use the same cadence. Invoice, externally billed, and canceling memberships are not supported.
+Retrieves a membership by ID or license key. Accessible to the account and to the membership's own user.
 </dd>
 </dl>
 </dd>
@@ -24040,10 +24089,7 @@ Updates a membership: merge metadata key-value pairs, toggle `cancel_at_period_e
 <dd>
 
 ```ruby
-client.memberships.update(
-  id: "id",
-  billing_period_days: 45
-)
+client.memberships.retrieve(id: "id")
 ```
 </dd>
 </dl>
@@ -24066,38 +24112,6 @@ client.memberships.update(
 <dl>
 <dd>
 
-**billing_period_days:** `Integer` — Number of days between recurring charges. Sets the current period end to the current period start plus this value and applies to every recurring variant. The new period end must remain in the future. Existing non-daily memberships cannot be changed to daily billing.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**cancel_at_period_end:** `Internal::Types::Boolean` — `true` cancels at the end of the current billing period (the customer keeps access until then); `false` reverses a pending cancellation.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**metadata:** `Internal::Types::Hash[String, Object]` — Key-value pairs to merge into the membership's metadata. Pass an empty object to clear it.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**payment_method_id:** `String` — The ID of a payment method the customer has saved with your account. Future renewals charge it, and an open past-due payment is retried on it right away. Requires the `member:payment_methods:manage` permission.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **request_options:** `Whop_sdk::Memberships::RequestOptions` 
     
 </dd>
@@ -24110,7 +24124,7 @@ client.memberships.update(
 </dl>
 </details>
 
-<details><summary><code>client.memberships.<a href="/lib/whop_sdk/memberships/client.rb">apply_promo_code</a>(id:, request) -> Whop_sdk::Types::Membership</code></summary>
+<details><summary><code>client.memberships.<a href="/lib/whop_sdk/memberships/client.rb">update</a>(id:, request) -> Whop_sdk::Types::Membership</code></summary>
 <dl>
 <dd>
 
@@ -24122,7 +24136,104 @@ client.memberships.update(
 <dl>
 <dd>
 
-Applies a promo code to an `active` or `trialing` membership that does not already have one and has exactly one recurring item. The discount lands on the next invoice and follows the code's duration (`once`, `repeating`, or `forever`). Works for Stripe-billed memberships and memberships billed by Whop's billing engine, including payment-element and multi-PSP renewals. Stock, plan eligibility, and expiry are still checked. Memberships with multiple recurring items are rejected.
+Updates a membership's metadata, scheduled cancellation, renewal payment method, or renewal cadence.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.memberships.update(
+  id: "id",
+  billing_period_days: 45
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**id:** `String` — Membership ID (`mem_` tag), or a software license key.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**billing_period_days:** `Integer` — Number of days between recurring charges. Sets the current period end to the current period start plus this value and applies to every recurring variant, so future renewals use the same cadence. The new period end must remain in the future. Only for active, trialing, or past-due memberships billed automatically by Whop; invoice, externally billed, and canceling memberships are not supported. Existing non-daily memberships cannot be changed to daily billing. Cannot be combined with other fields.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**cancel_at_period_end:** `Internal::Types::Boolean` — `true` cancels at the end of the current billing period (the customer keeps access until then); `false` reverses a pending cancellation.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**metadata:** `Internal::Types::Hash[String, Object]` — Key-value pairs to merge into the membership's metadata. Pass an empty object to clear it.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**payment_method_id:** `String` — The ID of a payment method the customer has saved with your account. Future renewals charge it, and an open past-due payment is retried on it right away. Requires the `member:payment_methods:manage` permission.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::Memberships::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.memberships.<a href="/lib/whop_sdk/memberships/client.rb">apply_promo_code</a>(id:, request) -> Whop_sdk::Types::Membership</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Applies a promo code to an `active` or `trialing` membership that does not already have one and has exactly one recurring item, for Stripe-billed memberships and memberships billed by Whop's billing engine. The discount lands on the next invoice and follows the code's duration (`once`, `repeating`, or `forever`).
 </dd>
 </dl>
 </dd>
@@ -24163,7 +24274,7 @@ client.memberships.apply_promo_code(
 <dl>
 <dd>
 
-**promo_code:** `String` — The promo code to apply, as customers enter it at checkout (for example `SAVE20`).
+**promo_code:** `String` — The promo code to apply, as customers enter it at checkout (for example `SAVE20`). Its stock, variant eligibility, and expiry are checked as at checkout.
     
 </dd>
 </dl>
@@ -24195,7 +24306,7 @@ client.memberships.apply_promo_code(
 <dl>
 <dd>
 
-Assigns an affiliate to a membership and pays them the commission you set on its future payments. Name the user with exactly one of `user_id`, `email`, or `username`. A user who is not yet an affiliate of your account becomes one, which also requires `affiliate:create`. Send a new `commission_type` or `commission_value` for the membership's current affiliate to change their commission; a membership that already has a different affiliate returns a conflict. Works for active or trialing memberships with one recurring plan that bill through Stripe or Whop's billing engine, and not for marketplace memberships, paused payments, or a scheduled cancellation. The payout cannot exceed 90% of the next renewal amount, and no past payments are recalculated. You cannot assign yourself.
+Assigns an affiliate to a membership and pays them the commission you set on its future payments; past payments are not recalculated. A user who is not yet an affiliate of your account becomes one, which also requires `affiliate:create`. Send a new `commission_type` or `commission_value` for the membership's current affiliate to change their commission; a membership that already has a different affiliate returns a conflict. Works for active or trialing memberships with one recurring variant that bill through Stripe or Whop's billing engine, and not for marketplace memberships, paused payments, or a scheduled cancellation. You cannot assign yourself.
 </dd>
 </dl>
 </dd>
@@ -24246,7 +24357,7 @@ client.memberships.assign_affiliate(
 <dl>
 <dd>
 
-**commission_value:** `Integer` — A whole number from 1 to 90 for `percentage`, or an amount greater than 1 in the membership currency for `flat_fee`. Flat fees need matching billing and settlement currencies.
+**commission_value:** `Integer` — A whole number from 1 to 90 for `percentage`, or an amount greater than 1 in the membership currency for `flat_fee`. The payout cannot exceed 90% of the next renewal amount. Flat fees need matching billing and settlement currencies.
     
 </dd>
 </dl>
@@ -24302,7 +24413,7 @@ client.memberships.assign_affiliate(
 <dl>
 <dd>
 
-Cancels a membership. Pass `cancel_at_period_end: true` to stop auto-renewal and keep access until the current billing period ends. Omit it (or pass `false`) to revoke access immediately. Buyers cannot cancel buy-now-pay-later (`splitit`, `sezzle`) or non-trial split-pay memberships.
+Cancels a membership, either immediately or at the end of the current billing period. Buyers cannot cancel buy-now-pay-later (`splitit`, `sezzle`) or non-trial split-pay memberships.
 </dd>
 </dl>
 </dd>
@@ -24348,6 +24459,14 @@ client.memberships.cancel(id: "id")
 <dl>
 <dd>
 
+**feedback_option_id:** `String` — The ID of the feedback option the customer picked as their reason for canceling, from the account's `feedback_options` preference. The membership records the option's label as the customer saw it and its category as `cancel_option`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **reason:** `String` — Free-form note recording why the membership was canceled.
     
 </dd>
@@ -24523,7 +24642,7 @@ client.memberships.pause(id: "id")
 <dl>
 <dd>
 
-Restores access to a `canceled` or `expired` membership that contains only one-time purchases and sets its `status` to `completed`. Lifetime memberships regain lifetime access. For memberships with an expiration, `days` sets `current_period_end` that many days from now; without it the original `current_period_end` is kept, so `days` is required once that has passed. Active and recurring memberships cannot be reactivated.
+Restores access to a `canceled` or `expired` membership that contains only one-time purchases and sets its `status` to `completed`. Lifetime memberships regain lifetime access; for memberships with an expiration, `days` sets the new `current_period_end`. Active and recurring memberships cannot be reactivated.
 </dd>
 </dl>
 </dd>
@@ -24780,7 +24899,7 @@ client.memberships.transfer(id: "id")
 <dl>
 <dd>
 
-Returns a paginated list of messages within a specific experience chat, DM, or group chat channel, sorted by creation time.
+Lists messages in an experience chat, DM, or group chat channel, sorted by creation time.
 
 Required permissions (one of):
  - `chat:read`
@@ -24891,7 +25010,7 @@ client.messages.list(
 <dl>
 <dd>
 
-Send a new message in an experience chat, DM, or group chat channel. Supports text content, attachments, polls, and replies.
+Sends a message in an experience chat, DM, or group chat channel. Supports text content, attachments, polls, and replies.
 
 Required permissions (one of):
  - `chat:message:create`
@@ -25070,7 +25189,7 @@ client.messages.retrieve(id: "id")
 <dl>
 <dd>
 
-Permanently delete a message from an experience chat, DM, or group chat channel. Only the message author or a channel admin can delete a message.
+Permanently deletes a message from an experience chat, DM, or group chat channel. Only the message author or a channel admin can delete a message.
 
 Required permissions (one of):
  - `chat:message:create` and `chat:read`
@@ -25138,7 +25257,7 @@ client.messages.delete(id: "id")
 <dl>
 <dd>
 
-Edit the content, attachments, or pinned status of an existing message in an experience chat, DM, or group chat channel.
+Edits the content, attachments, or pinned status of a message in an experience chat, DM, or group chat channel.
 
 Required permissions (one of):
  - `chat:message:create`
@@ -25231,7 +25350,7 @@ client.messages.update(id: "id")
 <dl>
 <dd>
 
-Lists the authenticated user's notifications, newest first. Requires a user credential — an account API key has no notification feed. Without filters the feed spans every experience the user belongs to plus the teams they are a member of. The `after` cursor is a notification `id` from a previous response; subsequent pages contain older notifications.
+Lists the authenticated user's notifications, newest first. Without filters the feed spans every experience the user belongs to plus the teams they are a member of. Requires a user credential — an account API key has no notification feed.
 </dd>
 </dl>
 </dd>
@@ -25524,7 +25643,7 @@ client.notifications.badges(experience_ids: ["exp_xxxxxxxxxxxxxx"])
 <dl>
 <dd>
 
-Marks the authenticated user's notifications as read: one experience's (`experience_id`) or everything (`all: true`) — exactly one of the two. Requires a user credential. Responds with the refreshed badge rows for the affected scope.
+Marks the authenticated user's notifications as read, for one experience or all of them, and returns the refreshed badge rows for that scope. Requires a user credential.
 </dd>
 </dl>
 </dd>
@@ -25594,7 +25713,7 @@ client.notifications.mark_read
 <dl>
 <dd>
 
-Retrieves a single notification by id — either an `id` returned by List Notifications, or the ephemeral id delivered with a push/websocket event. Requires a user credential.
+Retrieves a single notification, from the feed or from a push or websocket event. Requires a user credential.
 </dd>
 </dl>
 </dd>
@@ -25624,7 +25743,7 @@ client.notifications.retrieve(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — A notification `id` from List Notifications, or the id delivered with a push/websocket event.
+**id:** `String` — A notification `id` from List Notifications, or the ephemeral id delivered with a push or websocket event.
     
 </dd>
 </dl>
@@ -25799,7 +25918,7 @@ client.partner_referral_requests.list
 <dl>
 <dd>
 
-Creates a referral link or sends a verified partner's attribution request to an existing business or user for approval. Whop sessions creating a link with their own active `authorized_user_id` enroll automatically. Manual requests always require a verified partner. Recipients do not need to join the partner program.
+Creates a referral link, or sends an attribution request to an existing business or user for approval. Links require an enrolled partner who is not suspended; attribution requests require an enrolled, verified partner. Recipients do not need to join the partner program.
 </dd>
 </dl>
 </dd>
@@ -26164,7 +26283,7 @@ client.partners.create
 <dl>
 <dd>
 
-Ranks referrers by partner business earnings — all-time by default, or over the current day, month, year, or trailing 30 days. Authentication is optional: authenticated callers also get their own standing, anonymous callers get the rankings alone.
+Ranks referrers by partner business earnings over the chosen `period`, all-time by default. Authentication is optional: authenticated callers also get their own standing, anonymous callers get the rankings alone.
 </dd>
 </dl>
 </dd>
@@ -26226,7 +26345,7 @@ client.partners.leaderboard
 <dl>
 <dd>
 
-Lists the users the caller referred onto Whop, newest first by default, each with the caller's total affiliate earnings from that user across all tiers. Earnings sorting uses cached totals. Authorized staff can set user_id=global to list referrals across partners, with earnings for each user's current primary referrer.
+Lists the users the caller referred onto Whop, newest first by default, each with the caller's total affiliate earnings from that user across all tiers.
 </dd>
 </dl>
 </dd>
@@ -26256,14 +26375,6 @@ client.partners.referred_users
 <dl>
 <dd>
 
-**user_id:** `Whop_sdk::Partners::Types::ReferredUsersPartnersRequestUserID` — Set to global to view referred users across partners with each primary referrer's cached total earnings. Requires an admin or partner manager session; OAuth tokens and company API keys cannot use global mode. Optionally narrow to one earning_partner_id or earning_partner_username.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
 **earning_partner_id:** `String` — The selected referring partner's user_ ID. Requires user_id=global; cannot be combined with earning_partner_username.
     
 </dd>
@@ -26384,7 +26495,7 @@ client.partners.referred_users
 <dl>
 <dd>
 
-Retrieves the authenticated user's public profile, enrollment date, partner verification timestamp, verification waitlist status, partner certification completion, active direct business referral count, and default payout rates. Use me or the authenticated user's own user ID; other users are not accessible. Users who have not enrolled have a null joined_at. Create and manage referral links through /partner_referral_requests.
+Retrieves the authenticated user's partner profile: enrollment and verification status, certification completion, active direct business referral count, and default payout rates. Other users' profiles are not accessible. To create and manage referral links, use `/partner_referral_requests`.
 </dd>
 </dl>
 </dd>
@@ -26447,7 +26558,7 @@ client.partners.retrieve(id: "me")
 <dl>
 <dd>
 
-Lists payment method domains. Without `account_id`, returns the caller's own domains and those of every connected account.
+Lists the payment method domains registered for your account and its connected accounts.
 </dd>
 </dl>
 </dd>
@@ -26597,7 +26708,7 @@ client.payment_method_domains.list
 <dl>
 <dd>
 
-Registers a hostname with the wallet provider and attempts verification inline. Returns `verified` when the provider fetched the domain-association file (for Apple Pay, `/.well-known/apple-developer-merchantid-domain-association`), or `pending` when it could not — host the file, then retry with the verify endpoint.
+Registers a hostname with the wallet provider and attempts verification inline. Returns `verified` when the provider fetched the domain-association file (for Apple Pay, `/.well-known/apple-developer-merchantid-domain-association`), or `pending` when it could not: host the file, then retry with `POST /payment_method_domains/:id/verify`.
 </dd>
 </dl>
 </dd>
@@ -26612,7 +26723,7 @@ Registers a hostname with the wallet provider and attempts verification inline.
 <dd>
 
 ```ruby
-client.payment_method_domains.create(hostname: "pending.shinetime.example")
+client.payment_method_domains.create(hostname: "pending.shinetime.com")
 ```
 </dd>
 </dl>
@@ -26635,7 +26746,7 @@ client.payment_method_domains.create(hostname: "pending.shinetime.example")
 <dl>
 <dd>
 
-**hostname:** `String` — Hostname to register (e.g. `checkout.shinetime.example`).
+**hostname:** `String` — Hostname to register (e.g. `checkout.shinetime.com`).
     
 </dd>
 </dl>
@@ -26697,7 +26808,7 @@ client.payment_method_domains.retrieve(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — The unique identifier of the payment method domain, prefixed `pmd_`.
+**id:** `String` — The unique identifier of the payment method domain, prefixed `pmd_` or `dom_`.
     
 </dd>
 </dl>
@@ -26759,7 +26870,7 @@ client.payment_method_domains.delete(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — The unique identifier of the payment method domain, prefixed `pmd_`.
+**id:** `String` — The unique identifier of the payment method domain, prefixed `pmd_` or `dom_`.
     
 </dd>
 </dl>
@@ -26821,7 +26932,7 @@ client.payment_method_domains.verify(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — The unique identifier of the payment method domain, prefixed `pmd_`.
+**id:** `String` — The unique identifier of the payment method domain, prefixed `pmd_` or `dom_`.
     
 </dd>
 </dl>
@@ -26854,7 +26965,7 @@ client.payment_method_domains.verify(id: "id")
 <dl>
 <dd>
 
-Returns a paginated list of payment methods for a member or company, or for the authenticated user when neither is given, with optional filtering by creation date. A payment method is a stored representation of how a customer intends to pay, such as a card, bank account, or digital wallet.
+Returns a paginated list of saved payment methods for a member or account, or for the authenticated user when you pass neither.
 
 Required permissions:
  - `member:payment_methods:read`
@@ -27046,7 +27157,7 @@ client.payment_methods.list(
 <dl>
 <dd>
 
-Retrieves the details of an existing payment method. Addresses a member's wallet when member_id or account_id is given, otherwise your own.
+Retrieves a saved payment method from a member's wallet when you pass `member_id` or `account_id`, or from your own otherwise.
 
 Required permissions:
  - `member:payment_methods:read`
@@ -27217,7 +27328,7 @@ client.payment_methods.delete_payment_method(
 <dl>
 <dd>
 
-Prices a purchase the way a payment for it will be charged, for a buyer located by the shipping address, then the billing address, then the IP address you pass. The body is the `PaymentInput` a payment takes plus where the buyer is (`address`, `shipping_address`, `tax_ids`, `ip_address`); a seller that collects no tax on the purchase can be quoted without them. The purchase is priced from exactly what you send: no buyer is looked up, so no stored registration or purchase history applies. Quote what you are about to charge and pass the quote's `id` as `quote_id` when you create the payment: it then charges exactly the purchase, promo code and tax shown here. A quote is priced once, in the plans' own currency or the `presentment_currency` you ask for, and may be consumed by one payment before `expires_at`.
+Prices a purchase the way a payment for it will be charged. The body is the `PaymentInput` a payment takes plus where the buyer is, which a seller that collects no tax on the purchase can leave out. The purchase is priced from exactly what you send: no buyer is looked up, so no stored registration or purchase history applies. Pass the quote's `id` as `quote_id` when you create the payment to charge exactly the purchase, promo code, and tax shown here. A quote is priced once and may be consumed by one payment before `expires_at`. Cart entries must name existing variants with `plan_id`.
 </dd>
 </dl>
 </dd>
@@ -27263,6 +27374,14 @@ client.payment_quotes.create(account_id: "biz_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
+**line_items:** `Internal::Types::Array[Whop_sdk::PaymentQuotes::Types::CreatePaymentQuotesRequestLineItemsItem]` — What the buyer is purchasing. Each entry names an existing variant by plan_id. Several entries form a cart, which requires every variant to be compatible, belong to this account, and use the same currency.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **presentment_country:** `String` — The country to price the purchase for, as an ISO 3166-1 alpha-2 code such as `JP`, when the buyer chose one: a store's country picker. Prices in the currency `auto` would pick for a buyer in that country, so send it instead of `presentment_currency`, never with it. Whether a payment method can collect that currency is still judged where the buyer is: by `ip_address`, and by this country only without one. With no address that carries a country, tax is estimated for this country (`located_by` is `presentment_country`) at the country level, and a quote located this way is a preview a payment refuses with `quote_preview_only`. Send it only once the buyer has chosen a country: without it, an `ip_address` estimates more precisely, such as for a US state. For a country Whop has no currency for, the quote is priced as `auto` for the buyer's `ip_address`, and tax is still estimated for the country.
     
 </dd>
@@ -27319,7 +27438,7 @@ client.payment_quotes.create(account_id: "biz_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Retrieves a payment quote, including the payment holding it (`payment_id`, whose `status` says whether it collected) and when it expires.
+Retrieves a payment quote. Use it to check which payment holds the quote, through `payment_id`, and when it expires.
 </dd>
 </dl>
 </dd>
@@ -27374,6 +27493,20 @@ client.payment_quotes.retrieve(id: "id")
 <dl>
 <dd>
 
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Lists the payment rules on an account.
+</dd>
+</dl>
+</dd>
+</dl>
+
 #### 🔌 Usage
 
 <dl>
@@ -27486,6 +27619,20 @@ client.payment_rules.list
 <dl>
 <dd>
 
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Creates a payment rule. It is created `active` and applies its `action` to new payments that match all of its `conditions`.
+</dd>
+</dl>
+</dd>
+</dl>
+
 #### 🔌 Usage
 
 <dl>
@@ -27584,7 +27731,7 @@ client.payment_rules.create(
 <dl>
 <dd>
 
-Small and returned in full on one page.
+Lists the payment attributes a rule condition can read, with the operators and values each one accepts. Small and returned in full on one page.
 </dd>
 </dl>
 </dd>
@@ -27630,54 +27777,6 @@ client.payment_rules.list_fields
 <dl>
 <dd>
 
-#### 🔌 Usage
-
-<dl>
-<dd>
-
-<dl>
-<dd>
-
-```ruby
-client.payment_rules.retrieve(id: "id")
-```
-</dd>
-</dl>
-</dd>
-</dl>
-
-#### ⚙️ Parameters
-
-<dl>
-<dd>
-
-<dl>
-<dd>
-
-**id:** `String` — The payment rule ID.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**request_options:** `Whop_sdk::PaymentRules::RequestOptions` 
-    
-</dd>
-</dl>
-</dd>
-</dl>
-
-
-</dd>
-</dl>
-</details>
-
-<details><summary><code>client.payment_rules.<a href="/lib/whop_sdk/payment_rules/client.rb">delete</a>(id:) -> </code></summary>
-<dl>
-<dd>
-
 #### 📝 Description
 
 <dl>
@@ -27686,7 +27785,7 @@ client.payment_rules.retrieve(id: "id")
 <dl>
 <dd>
 
-The rule stops applying to new payments and is kept, so the payments it already decided still name it.
+Retrieves a payment rule.
 </dd>
 </dl>
 </dd>
@@ -27701,7 +27800,7 @@ The rule stops applying to new payments and is kept, so the payments it already
 <dd>
 
 ```ruby
-client.payment_rules.delete(id: "id")
+client.payment_rules.retrieve(id: "id")
 ```
 </dd>
 </dl>
@@ -27736,7 +27835,7 @@ client.payment_rules.delete(id: "id")
 </dl>
 </details>
 
-<details><summary><code>client.payment_rules.<a href="/lib/whop_sdk/payment_rules/client.rb">update</a>(id:, request) -> Whop_sdk::Types::PaymentRule</code></summary>
+<details><summary><code>client.payment_rules.<a href="/lib/whop_sdk/payment_rules/client.rb">delete</a>(id:) -> </code></summary>
 <dl>
 <dd>
 
@@ -27748,7 +27847,7 @@ client.payment_rules.delete(id: "id")
 <dl>
 <dd>
 
-Changes the rule's name or metadata, keeping its ID and everything recorded against it. What the rule *does* is fixed once created, so the payments it decided keep naming the rule that decided them; use replace to change that.
+Deletes a payment rule. It stops applying to new payments but is kept, so the payments it already decided still name it.
 </dd>
 </dl>
 </dd>
@@ -27763,71 +27862,7 @@ Changes the rule's name or metadata, keeping its ID and everything recorded agai
 <dd>
 
 ```ruby
-client.payment_rules.update(id: "id")
-```
-</dd>
-</dl>
-</dd>
-</dl>
-
-#### ⚙️ Parameters
-
-<dl>
-<dd>
-
-<dl>
-<dd>
-
-**id:** `String` — The payment rule ID.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**metadata:** `Internal::Types::Hash[String, String]` — Custom string-to-string values for your integration. Maximum 50 keys, 40 characters per key, 500 characters per value.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**name:** `String` — A name for this rule. Up to 255 characters.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**request_options:** `Whop_sdk::PaymentRules::RequestOptions` 
-    
-</dd>
-</dl>
-</dd>
-</dl>
-
-
-</dd>
-</dl>
-</details>
-
-<details><summary><code>client.payment_rules.<a href="/lib/whop_sdk/payment_rules/client.rb">activate</a>(id:) -> Whop_sdk::Types::PaymentRule</code></summary>
-<dl>
-<dd>
-
-#### 🔌 Usage
-
-<dl>
-<dd>
-
-<dl>
-<dd>
-
-```ruby
-client.payment_rules.activate(id: "id")
+client.payment_rules.delete(id: "id")
 ```
 </dd>
 </dl>
@@ -27862,7 +27897,7 @@ client.payment_rules.activate(id: "id")
 </dl>
 </details>
 
-<details><summary><code>client.payment_rules.<a href="/lib/whop_sdk/payment_rules/client.rb">deactivate</a>(id:) -> Whop_sdk::Types::PaymentRule</code></summary>
+<details><summary><code>client.payment_rules.<a href="/lib/whop_sdk/payment_rules/client.rb">update</a>(id:, request) -> Whop_sdk::Types::PaymentRule</code></summary>
 <dl>
 <dd>
 
@@ -27874,7 +27909,147 @@ client.payment_rules.activate(id: "id")
 <dl>
 <dd>
 
-The rule stops applying to new payments. It keeps its ID and can be activated again.
+Updates a payment rule's name or metadata, keeping its ID and everything recorded against it. A rule's `action` and `conditions` are fixed once created, so the payments it decided keep naming the rule that decided them; use `POST /payment_rules/:id/replace` to change them.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.payment_rules.update(id: "id")
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**id:** `String` — The payment rule ID.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**metadata:** `Internal::Types::Hash[String, String]` — Custom string-to-string values for your integration. Maximum 50 keys, 40 characters per key, 500 characters per value.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**name:** `String` — A name for this rule. Up to 255 characters.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::PaymentRules::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.payment_rules.<a href="/lib/whop_sdk/payment_rules/client.rb">activate</a>(id:) -> Whop_sdk::Types::PaymentRule</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Activates an inactive payment rule so it applies to new payments again. A deleted rule cannot be activated.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.payment_rules.activate(id: "id")
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**id:** `String` — The payment rule ID.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::PaymentRules::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.payment_rules.<a href="/lib/whop_sdk/payment_rules/client.rb">deactivate</a>(id:) -> Whop_sdk::Types::PaymentRule</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Deactivates a payment rule so it stops applying to new payments. It keeps its ID and can be activated again.
 </dd>
 </dl>
 </dd>
@@ -27936,7 +28111,7 @@ client.payment_rules.deactivate(id: "id")
 <dl>
 <dd>
 
-Deletes this rule and creates its successor in one step. The successor carries a new ID and the metadata of the rule it replaced,.
+Changes a payment rule's `action` and `conditions` by deleting it and creating its successor in one step. The successor has a new ID and keeps the replaced rule's name, metadata, and `active` or `inactive` status.
 </dd>
 </dl>
 </dd>
@@ -28025,7 +28200,7 @@ client.payment_rules.replace(
 <dl>
 <dd>
 
-Lists payments, newest first. By default, returns account sales: a company credential's own account, or for a user every account they can read payments for. Set `mode=user_sales` to list only the sales received by the signed-in user's primary ledger account, without a company. This mode requires the user's own Whop login session and cannot be combined with `account_id`. Filters narrow by account, buyer, product, plan, membership, status, billing reason, currency, and creation window. Filtering by `billing_reason=subscription_cycle` also matches renewals recorded as `subscription_update`. `settlement_time_at` is null on list rows — retrieve the payment for it.
+Lists payments, newest first. By default, returns sales for the accounts your credential can read: an account credential's own account, or every account a user can read payments for. Set `mode` to `user_sales` to list the sales the signed-in user received personally, outside any account.
 </dd>
 </dl>
 </dd>
@@ -28055,7 +28230,7 @@ client.payments.list
 <dl>
 <dd>
 
-**mode:** `Whop_sdk::Payments::Types::ListPaymentsRequestMode` — Which sales to list. `account_sales` returns sales for the accounts the caller can read. `user_sales` returns only sales received by the signed-in user's primary ledger account, without a company; requires their own Whop login session and cannot be combined with `account_id`.
+**mode:** `Whop_sdk::Payments::Types::ListPaymentsRequestMode` — Which sales to list. `account_sales` returns sales for the accounts the caller can read. `user_sales` returns only sales the signed-in user received personally, outside any account; it requires the user's own Whop login session and cannot be combined with `account_id`.
     
 </dd>
 </dl>
@@ -28079,7 +28254,7 @@ client.payments.list
 <dl>
 <dd>
 
-**billing_reason:** `Whop_sdk::Payments::Types::ListPaymentsRequestBillingReason` — Only payments charged for this reason.
+**billing_reason:** `Whop_sdk::Payments::Types::ListPaymentsRequestBillingReason` — Only payments charged for this reason. `subscription_cycle` also matches renewals recorded as `subscription_update`.
     
 </dd>
 </dl>
@@ -28231,7 +28406,7 @@ client.payments.list
 <dl>
 <dd>
 
-Charges a buyer for one or more variants. Pass a payment method already on file (`member_id` and `payment_method_id`), or a `confirmation_token` describing a method the buyer just supplied. Collection runs in the background: the response is the payment as created, not its outcome — poll Retrieve status for how far it has got and, for a confirmation-token payment, what the buyer must still do. Pass `line_items` for one or more variants with quantities, `plan_id` for an existing variant, or the compatibility input `plan` to find or create one inline. These inputs are mutually exclusive.
+Charges a buyer for one or more variants with a payment method already on file (`member_id` and `payment_method_id`), or with a `confirmation_token` for a method the buyer just supplied. Collection runs in the background, so the response is the payment as created, not its outcome: poll Retrieve payment status for how far it has got and what the buyer must still do.
 </dd>
 </dl>
 </dd>
@@ -28309,6 +28484,14 @@ client.payments.create(account_id: "biz_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
+**line_items:** `Internal::Types::Array[Whop_sdk::Payments::Types::CreatePaymentsRequestLineItemsItem]` — What the buyer is purchasing. Each entry takes exactly one of `plan_id` or an inline `plan`. One entry charges that variant; several entries form a cart, which requires every variant to be compatible, belong to this account, and use the same currency. Mutually exclusive with `plan_id` and `plan`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **member_id:** `String` — The member to charge, prefixed `mber_`. Required with `payment_method_id` unless `confirmation_token` is provided.
     
 </dd>
@@ -28349,7 +28532,7 @@ client.payments.create(account_id: "biz_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-**quote_id:** `String` — A payment quote from `POST /payment_quotes`, prefixed `pq_`. The payment charges exactly the quote: its purchase (its variants and quantities, or the `plan` it priced), which this body may then omit, its promo code, and its tax, the quote's `tax_amount` rather than a figure calculated now. Omit it, or send null, to have tax calculated when the payment is charged. The quote must belong to `account_id`. A purchase field you omit or send as null takes the quote's value; the buyer's email, the addresses and the payment method are this request's own, never the quote's. Whatever you do send must describe the quoted purchase: the same variants, quantities and promo code. A quote that priced `plan` takes only the same `plan` you sent to `POST /payment_quotes` (or omit the purchase to take the quoted one), never `plan_id` or `line_items`, and a quote that priced variants by id never takes `plan`. Unless the quote located no buyer (`located_by` is null), the address the payment carries (its shipping address, else its billing address) must put the buyer where the quote priced tax, by country, state and postal code; otherwise the payment is refused with 400 before the payment method is used. A quote located by IP address or by the country the buyer chose (`located_by` is `ip_address` or `presentment_country`) is a preview and cannot be paid. A quote is consumed by one payment: a declined payment keeps it and can be retried; a new payment needs a new quote. A quote cannot be charged through PayPal; such a payment is refused before the payment method is used. A quote priced in a `presentment_currency` is charged in that currency at the quote's `exchange_rate`. A payment refused over its quote carries an error `code`. `quote_expired`: the quote has expired; quote again. `quote_tax_unavailable`: the quote could not price tax; quote again, or omit `quote_id`. `quote_preview_only`: the quote was located by IP address or by the country the buyer chose; quote again with the buyer's address. `quote_in_use` (409): another payment holds the quote. `quote_mismatch`: the purchase or the buyer's address is not the one quoted. `quote_rate_expired`: the exchange rate the quote was priced at has moved too far to charge; quote again. `payment_method_currency_unsupported`: the payment method cannot pay in the quote's currency; use another method, or quote again in another currency. `quote_processor_unsupported`: the payment method cannot pay a quote, as with PayPal; use another method, or omit `quote_id` to have tax calculated when the payment is charged.
+**quote_id:** `String` — A payment quote from `POST /payment_quotes`, prefixed `pq_`. The payment charges exactly the quote: its purchase (its variants and quantities, or the `plan` it priced), which this body may then omit, its promo code, and its tax, the quote's `tax_amount` rather than a figure calculated now. Omit it, or send null, to have tax calculated when the payment is charged. The quote must belong to `account_id`. A purchase field you omit or send as null takes the quote's value; the buyer's email, the addresses and the payment method are this request's own, never the quote's. Whatever you do send must describe the quoted purchase: the same variants, quantities and promo code. A quote that priced `plan` takes only the same `plan` you sent to `POST /payment_quotes` (or omit the purchase to take the quoted one), never `plan_id` or `line_items`, and a quote that priced variants by id never takes `plan`. Unless the quote located no buyer (`located_by` is null), the address the payment carries (its shipping address, else its billing address) must put the buyer where the quote priced tax, by country, state and postal code; otherwise the payment is refused with 400 before the payment method is used. A quote located by IP address or by the country the buyer chose (`located_by` is `ip_address` or `presentment_country`) is a preview and cannot be paid. A quote is consumed by one payment: a declined payment keeps it and can be retried; a new payment needs a new quote. A quote cannot be charged by a processor that doesn't take quotes, such as a seller's own connected PayPal account; such a payment is refused before the payment method is used. A quote priced in a `presentment_currency` is charged in that currency at the quote's `exchange_rate`. A payment refused over its quote carries an error `code`. `quote_expired`: the quote has expired; quote again. `quote_tax_unavailable`: the quote could not price tax; quote again, or omit `quote_id`. `quote_preview_only`: the quote was located by IP address or by the country the buyer chose; quote again with the buyer's address. `quote_in_use` (409): another payment holds the quote. `quote_mismatch`: the purchase or the buyer's address is not the one quoted. `quote_rate_expired`: the exchange rate the quote was priced at has moved too far to charge; quote again. `payment_method_currency_unsupported`: the payment method cannot pay in the quote's currency; use another method, or quote again in another currency. `quote_processor_unsupported`: the payment would be processed by a processor that doesn't take quotes, such as a seller's own connected PayPal account; use another method, or omit `quote_id` to have tax calculated when the payment is charged.
     
 </dd>
 </dl>
@@ -28467,7 +28650,7 @@ client.payments.retrieve(id: "id")
 <dl>
 <dd>
 
-Updates a payment's `shipping_address` or `return_url`. Send the complete `shipping_address`, because it replaces the existing address and any field you leave out is cleared.
+Updates a payment's `shipping_address` or `return_url`.
 </dd>
 </dl>
 </dd>
@@ -28731,7 +28914,7 @@ client.payments.generate_pdf(id: "id")
 <dl>
 <dd>
 
-Issues a full or partial refund for a payment. The refund is processed through the original payment processor and the membership status is updated accordingly.
+Refunds all or part of a payment through the processor that charged it, and updates its membership to match. The buyer is emailed, the affiliate commission on the payment is clawed back, and any open Resolution Center case on the payment is closed.
 </dd>
 </dl>
 </dd>
@@ -28801,7 +28984,7 @@ client.payments.refund(id: "id")
 <dl>
 <dd>
 
-Retries a failed or pending payment. This re-attempts the charge using the original payment method and variant details.
+Charges an unpaid payment again with its original payment method and variant. A payment can typically be retried once, and only while its membership is active, trialing or past due, or when it is a membership's failed first payment.
 </dd>
 </dl>
 </dd>
@@ -28913,7 +29096,7 @@ client.payments.void(id: "id")
 </dl>
 </details>
 
-<details><summary><code>client.payments.<a href="/lib/whop_sdk/payments/client.rb">resume</a>(payment_id:) -> Whop_sdk::Types::PaymentStatus</code></summary>
+<details><summary><code>client.payments.<a href="/lib/whop_sdk/payments/client.rb">resume</a>(payment_id:, request) -> Whop_sdk::Types::PaymentStatus</code></summary>
 <dl>
 <dd>
 
@@ -28925,7 +29108,7 @@ client.payments.void(id: "id")
 <dl>
 <dd>
 
-Starts a fresh on-session attempt with the saved card for a subscription renewal that is waiting on the customer to authenticate; the bank's step then arrives in `next_action` on the following status reads. Only the payment's own customer may call it — with the payment's `client_secret` or their own session — and it is a no-op for any payment that is not a parked renewal.
+Charges the saved card again, with the buyer present, for a payment their bank declined until they authenticate (such as with 3DS). Retrieve the payment afterward to get the bank's challenge from `next_action`; once the buyer completes it, they land on `return_url`, or on Whop's hosted verification page if none was given. Only the buyer can call this, with the payment's `client_secret`, an OAuth token for their own account with the `member:payment_methods:use` scope, or the token from a verified `payment` session intent. An API key gets a `403`. Has no effect on a payment that is not waiting on authentication.
 </dd>
 </dl>
 </dd>
@@ -28963,6 +29146,14 @@ client.payments.resume(payment_id: "payment_id")
 <dl>
 <dd>
 
+**return_url:** `String` — Where the buyer continues after completing an off-site step. Must be an absolute https URL without credentials (http is allowed for localhost), at most 2,048 characters. Defaults to Whop's hosted verification page. Ignored when the payment is not waiting on authentication.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **request_options:** `Whop_sdk::Payments::RequestOptions` 
     
 </dd>
@@ -29189,7 +29380,7 @@ client.payout_accounts.retrieve(id: "poact_xxxxxxxxxxxx")
 <dl>
 <dd>
 
-Returns a list of active payout methods configured for a company, ordered by most recently created.
+Lists the active payout methods configured for an account, newest first.
 
 Required permissions:
  - `payout:destination:read`
@@ -29659,7 +29850,7 @@ client.payouts.create(
 <dl>
 <dd>
 
-Creates a short-lived, provider-backed quote for a payout. No funds move until the returned quote_token is submitted to POST /payouts. An Idempotency-Key header is required.
+Creates a short-lived, provider-backed quote of a payout's fee, exchange rate, and destination amount. No funds move until you submit the returned `quote_token` to `POST /payouts`.
 </dd>
 </dl>
 </dd>
@@ -29780,7 +29971,7 @@ client.payouts.create_quote(
 <dl>
 <dd>
 
-Fetches one payout by its `wdrl_` ID, or by the `cofr_` conversion request ID a stablecoin payout carries as `payout_request_id` — both ids answer with the same payout object. Authentication is optional. Anyone with the ID can view payout tracking details, including notes, trace code, exchange rate, and payout request ID. Accounting fields require payout:withdrawal:read on the owning ledger. A supplied invalid credential returns 401.
+Retrieves a payout by its `wdrl_` ID, or by the `cofr_` conversion request ID a stablecoin payout carries as `payout_request_id`. Authentication is optional: anyone with the ID can view tracking details, including notes, trace code, exchange rate, and payout request ID, while accounting fields require `payout:withdrawal:read` on the account or user that owns the payout. A supplied invalid credential returns 401.
 </dd>
 </dl>
 </dd>
@@ -29858,7 +30049,7 @@ client.payouts.retrieve(id: "id")
 <dl>
 <dd>
 
-Cancels a payout that is still in review and returns the funds, fees included, to the balance. A payout can be canceled while its status is `in_review`. A `requested` payout is still being prepared (its funds may be converting) and answers 409 until it reaches review; from `processing` on, the money is on its way and the answer is 409 with error type `not_cancelable`. Canceling a payout that is already canceled succeeds and returns it unchanged.
+Cancels a payout whose `status` is `in_review` and returns the funds, fees included, to the balance. A `requested` payout is still being prepared (its funds may be converting) and returns 409 until it reaches review; from `processing` on, the money is on its way and the response is 409 with error type `not_cancelable`. Canceling an already-canceled payout succeeds and returns it unchanged.
 </dd>
 </dl>
 </dd>
@@ -29937,7 +30128,7 @@ client.payouts.cancel(id: "id")
 <dl>
 <dd>
 
-Lists the people (visitors and customers) of an account: the identity-linked person profiles aggregated from every pixel, payment, and platform event — identities, purchases and LTV, geo/device profile, traffic sources, and first/last marketing touches.
+Lists the people (visitors and customers) of an account: identity-linked profiles assembled from every pixel, payment, and platform event. Filter and sort them to segment an account's audience.
 </dd>
 </dl>
 </dd>
@@ -30354,7 +30545,7 @@ client.people.list(
 <dl>
 <dd>
 
-Retrieves one person for an account. The identifier can be a person ID (prefixed `prsn_`), a user ID (prefixed `user_`), an email address, or a phone number — merged people resolve to the surviving profile.
+Retrieves one person for an account, looked up by person ID, user ID, email address, or phone number.
 </dd>
 </dl>
 </dd>
@@ -30384,7 +30575,7 @@ client.people.retrieve(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — The person ID, user ID, email address, or phone number to look up.
+**id:** `String` — The person ID (prefixed `prsn_`), user ID (prefixed `user_`), email address, or phone number to look up. A merged person resolves to the surviving profile.
     
 </dd>
 </dl>
@@ -31334,7 +31525,7 @@ client.plans.update(id: "id")
 <dl>
 <dd>
 
-Deprecated compatibility endpoint. Preview variant tax with `POST /variants/{id}/calculate_tax` instead.
+Deprecated compatibility endpoint. Quote tax with `POST /payment_quotes` instead.
 </dd>
 </dl>
 </dd>
@@ -31559,7 +31750,7 @@ client.product_affiliates.list(
 <dl>
 <dd>
 
-Returns a paginated list of products. Omit `account_id` to search the public marketplace.
+Lists an account's products, or searches the public marketplace when you omit `account_id`.
 </dd>
 </dl>
 </dd>
@@ -31966,7 +32157,7 @@ client.products.create(title: "Interior Deep Clean")
 <dl>
 <dd>
 
-Retrieves a product. Public — no credentials.
+Retrieves a product. Requires no authentication.
 </dd>
 </dl>
 </dd>
@@ -32357,7 +32548,7 @@ client.products.unpublish(id: "id")
 <dl>
 <dd>
 
-Lists promo codes for an account with cursor pagination, filters, and sorting.
+Lists an account's promo codes.
 </dd>
 </dl>
 </dd>
@@ -33279,7 +33470,7 @@ client.reactions.delete(id: "reac_xxxxxxxxxxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Lists refunds, newest first. Without filters this is every refund the caller can read; narrow it to one payment with `payment_id`, one account with `account_id`, or one buyer with `user_id`.
+Lists refunds the caller can read, newest first. Filter by payment, account, or buyer to narrow the results.
 </dd>
 </dl>
 </dd>
@@ -34476,7 +34667,7 @@ client.resolution_center_cases.withdraw(id: "id")
 <dl>
 <dd>
 
-Returns a paginated list of customer reviews for a specific product, with optional filtering by star rating and creation date.
+Lists the published reviews for a product or account. Without `account_id` or `product_id`, a user lists the reviews they wrote, an account or app API key lists its account's reviews, and a request without credentials returns 400.
 </dd>
 </dl>
 </dd>
@@ -34492,13 +34683,8 @@ Returns a paginated list of customer reviews for a specific product, with option
 
 ```ruby
 client.reviews.list(
-  first: 42,
-  last: 42,
-  product_id: "prod_xxxxxxxxxxxxx",
-  min_stars: 42,
-  max_stars: 42,
-  created_before: "2023-12-01T05:00:00Z",
-  created_after: "2023-12-01T05:00:00Z"
+  account_id: "biz_xxxxxxxxxxxxxx",
+  product_id: "prod_xxxxxxxxxxxxx"
 )
 ```
 </dd>
@@ -34514,7 +34700,7 @@ client.reviews.list(
 <dl>
 <dd>
 
-**after:** `String` — Returns the elements in the list that come after the specified cursor.
+**account_id:** `String` — The unique identifier of the account to list reviews for.
     
 </dd>
 </dl>
@@ -34522,7 +34708,7 @@ client.reviews.list(
 <dl>
 <dd>
 
-**before:** `String` — Returns the elements in the list that come before the specified cursor.
+**product_id:** `String` — The unique identifier of the product to list reviews for.
     
 </dd>
 </dl>
@@ -34530,7 +34716,7 @@ client.reviews.list(
 <dl>
 <dd>
 
-**first:** `Integer` — Returns the first _n_ elements from the list.
+**min_stars:** `Integer` — The minimum star rating to include in results, from 1 to 5 inclusive.
     
 </dd>
 </dl>
@@ -34538,7 +34724,7 @@ client.reviews.list(
 <dl>
 <dd>
 
-**last:** `Integer` — Returns the last _n_ elements from the list.
+**max_stars:** `Integer` — The maximum star rating to include in results, from 1 to 5 inclusive.
     
 </dd>
 </dl>
@@ -34546,7 +34732,7 @@ client.reviews.list(
 <dl>
 <dd>
 
-**product_id:** `String` — The unique identifier of the product to list reviews for.
+**created_before:** `String` — Only return reviews created before this timestamp.
     
 </dd>
 </dl>
@@ -34554,7 +34740,7 @@ client.reviews.list(
 <dl>
 <dd>
 
-**min_stars:** `Integer` — The minimum star rating to include in results, from 1 to 5 inclusive.
+**created_after:** `String` — Only return reviews created after this timestamp.
     
 </dd>
 </dl>
@@ -34562,7 +34748,7 @@ client.reviews.list(
 <dl>
 <dd>
 
-**max_stars:** `Integer` — The maximum star rating to include in results, from 1 to 5 inclusive.
+**order:** `Whop_sdk::Reviews::Types::ListReviewsRequestOrder` — The field to sort reviews by.
     
 </dd>
 </dl>
@@ -34570,7 +34756,7 @@ client.reviews.list(
 <dl>
 <dd>
 
-**created_before:** `String` — Only return reviews created before this timestamp.
+**direction:** `Whop_sdk::Reviews::Types::ListReviewsRequestDirection` — The sort direction.
     
 </dd>
 </dl>
@@ -34578,7 +34764,31 @@ client.reviews.list(
 <dl>
 <dd>
 
-**created_after:** `String` — Only return reviews created after this timestamp.
+**first:** `Integer` — Number of results to return from the start of the range.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**after:** `String` — Return results after this cursor. Use `page_info.end_cursor` from the previous response to fetch the next page.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**last:** `Integer` — Number of results to return from the end of the range.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**before:** `String` — Return results before this cursor. Use `page_info.start_cursor` from the previous response to fetch the previous page.
     
 </dd>
 </dl>
@@ -34610,7 +34820,7 @@ client.reviews.list(
 <dl>
 <dd>
 
-Retrieves the details of an existing review.
+Retrieves a published review. Reviews that are not published return 404.
 </dd>
 </dl>
 </dd>
@@ -34640,7 +34850,69 @@ client.reviews.retrieve(id: "rev_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-**id:** `String` — The unique identifier of the review to retrieve.
+**id:** `String` — The unique identifier of the review.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::Reviews::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.reviews.<a href="/lib/whop_sdk/reviews/client.rb">delete</a>(id:) -> Whop_sdk::Reviews::Types::DeleteReviewsResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Deletes a review the signed-in user wrote. Requires the `review:delete` scope, and returns 404 for a review another user wrote.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.reviews.delete(id: "rev_xxxxxxxxxxxxxx")
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**id:** `String` — The unique identifier of the review.
     
 </dd>
 </dl>
@@ -34673,7 +34945,7 @@ client.reviews.retrieve(id: "rev_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Lists setup intents newest first. An account API key lists its own account; a user token lists every account it can read, or one account with `account_id`. `client_secret` is always null on list rows — retrieve the setup intent for it.
+Lists setup intents newest first. An account API key lists its own account; a user token lists every account it can read, or one account with `account_id`.
 </dd>
 </dl>
 </dd>
@@ -34807,7 +35079,7 @@ client.setup_intents.list
 <dl>
 <dd>
 
-Saves a buyer's payment method for later without charging it. Pass a `confirmation_token` for a method the buyer just supplied through the payment elements in setup mode, or a `payment_method_id` already on file to re-verify it. The response is the setup intent as created, not its outcome: it is `processing` while the payment method is saved in the background, and `requires_action` when the buyer still has a step. Hand `client_secret` to the elements' `handleNextAction`, or poll Retrieve setup status, for the outcome. A buyer's own token holding `member:payment_methods:use` may create a setup intent for itself from a confirmation token.
+Saves a buyer's payment method for later without charging it — one the buyer just supplied through the payment elements in setup mode, or one already on file to re-verify. The setup completes in the background, so the response is the setup intent as created, not its outcome: hand `client_secret` to the elements' `handleNextAction`, or poll Retrieve setup status. A buyer's own token holding `member:payment_methods:use` may create a setup intent for itself from a confirmation token.
 </dd>
 </dl>
 </dd>
@@ -34933,7 +35205,7 @@ client.setup_intents.create(account_id: "biz_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Returns one setup intent. Related records are ids — once `status` is `succeeded`, `payment_method_id` is the saved method to charge or retrieve. The buyer's own token may retrieve a setup intent that belongs to it.
+Retrieves a setup intent. Once its `status` is `succeeded`, charge the saved method by its `payment_method_id`. The buyer's own token may retrieve a setup intent that belongs to it.
 </dd>
 </dl>
 </dd>
@@ -35131,7 +35403,7 @@ client.setup_intents.retrieve_status(setup_intent_id: "setup_intent_id")
 <dl>
 <dd>
 
-Returns a paginated list of shipments for an account.
+Lists an account's shipments.
 </dd>
 </dl>
 </dd>
@@ -35354,7 +35626,7 @@ client.shipments.create(
 <dl>
 <dd>
 
-Retrieves a shipment by its id, or by the payment id it fulfills.
+Retrieves a shipment by its ID, or by the ID of the payment it fulfills.
 </dd>
 </dl>
 </dd>
@@ -36366,7 +36638,7 @@ client.social_accounts.refresh(id: "id")
 <dl>
 <dd>
 
-Deprecated. Lists every metric, which no longer says which of them a projection accepts. List the ones you can chart with `GET /stats/time_series`. Aggregates that are not bucketed over time are reports, listed at `GET /stats/reports`.
+Deprecated. Lists every metric without saying which ones you can chart. List chartable metrics with `GET /stats/time_series`, and aggregates that are not bucketed over time with `GET /stats/reports`.
 </dd>
 </dl>
 </dd>
@@ -36777,7 +37049,7 @@ client.stats.retrieve(
 <dl>
 <dd>
 
-**steps:** `Whop_sdk::Types::RetrieveStatsRequestSteps` — Funnel only. Required when metric=funnel. Consecutive one-based steps encoded as steps[1][event], steps[1][page], steps[2][event], and so on. Values are scalar strings, never JSON.
+**steps:** `Whop_sdk::Types::RetrieveStatsRequestSteps` — Funnel only. Required when metric=funnel. 2 to 10 ordered events per person, as consecutive one-based bracket parameters such as `steps[1][event]=pixel.page&steps[1][page]=/pricing*&steps[2][event]=payment.completed`. Values are scalar strings, never JSON. A person's first step 1 match inside `from`/`to` anchors their cohort, breakdown, and conversion window; later matches do not restart it. Other events may occur between steps, and conversions may land after `to`. For an experiment funnel, make `experiment.exposure` step 1 and pass `breakdown_by=variant`.
     
 </dd>
 </dl>
@@ -37050,7 +37322,7 @@ client.stats.retrieve(
 <dl>
 <dd>
 
-Returns a paginated list of support channels for a specific company, with optional filtering by resolution status and custom sorting.
+Lists support channels between an account's team and its customers, most recently active first by default. Pass `open=true` to find channels awaiting a support response.
 
 Required permissions:
  - `support_chat:read`
@@ -37135,6 +37407,38 @@ client.support_channels.list(
 <dl>
 <dd>
 
+**customer_user_id:** `String` — Only return support channels opened by this customer.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**participated:** `Internal::Types::Boolean` — Set to true to only return channels the authenticated user has joined as a participant. Requires a user.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**include_last_message:** `Internal::Types::Boolean` — Set to true to return `last_message` and `unread` on each channel. Both are `null` otherwise, which keeps large lists fast.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**include_participated:** `Internal::Types::Boolean` — Set to true to return `participated` on each channel. It is `null` otherwise, which keeps large lists fast.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **direction:** `Whop_sdk::Types::Direction` 
     
 </dd>
@@ -37183,7 +37487,7 @@ client.support_channels.list(
 <dl>
 <dd>
 
-Open a new support channel between a company team member and a customer. Returns the existing channel if one already exists for that user.
+Opens a support channel between an account's team and a customer. Returns the existing channel if that customer already has one.
 
 Required permissions:
  - `support_chat:create`
@@ -37341,7 +37645,7 @@ client.support_channels.retrieve(id: "id")
 <dl>
 <dd>
 
-Retrieve the account's completed or pending swaps — currently just the latest one.
+Lists the completed or pending swaps for an account or user — currently only the most recent one.
 </dd>
 </dl>
 </dd>
@@ -37411,7 +37715,7 @@ client.swaps.list
 <dl>
 <dd>
 
-Swaps one token for another from the account's wallet, or converts between fiat currencies in the account's ledger at the mid-market rate. Crypto swaps finish in the background — check the swap for its status.
+Swaps one token for another in an account or user's wallet, or converts between their fiat balances at the mid-market rate. Crypto swaps finish in the background — retrieve the swap to follow its status.
 </dd>
 </dl>
 </dd>
@@ -37540,7 +37844,7 @@ client.swaps.create(
 <dl>
 <dd>
 
-Previews the price of a swap. Fiat pairs quote the in-ledger mid-market conversion — the same rate creating the swap fills at. No funds move and nothing is saved.
+Previews the price of a swap before you create it. Fiat pairs quote the mid-market rate — the same rate creating the swap fills at. No funds move, nothing is saved, and no authentication is required.
 </dd>
 </dl>
 </dd>
@@ -37670,7 +37974,7 @@ client.swaps.create_quote(
 <dl>
 <dd>
 
-Retrieves a single swap and its status.
+Retrieves a swap and its status. Poll it after creating a crypto swap, which finishes in the background.
 </dd>
 </dl>
 </dd>
@@ -37733,7 +38037,7 @@ client.swaps.retrieve(id: "id")
 <dl>
 <dd>
 
-Lists an account's team members, including pending invites (`status: "pending"`, `ausri_` ids; `user` is `null` for invites sent to an email with no Whop account yet). For accepted members, `email` requires the `company:authorized_user:email:read` scope and is `null` otherwise. A user credential with `company:basic:read` may list only its own joined membership by passing its own `user_id` and `status=joined`. Listing `role=workforce` is also allowed with the `bounty:create` scope.
+Lists an account's team members, including pending invites. A user credential with `company:basic:read` may list only its own joined membership by passing its own `user_id` and `status=joined`. Listing `role=workforce` is also allowed with the `bounty:create` scope.
 </dd>
 </dl>
 </dd>
@@ -37883,7 +38187,7 @@ client.team_members.list(account_id: "account_id")
 <dl>
 <dd>
 
-Adds a member to an account's team with a system role. Identify them by exactly one of `user_id` or `email`. If the person has not yet accepted — or the email does not belong to a Whop account yet — an invitation is sent instead and the response is `202` with `{ "object": "team_member_invite", "invitation_sent": true }`. If they already have a pending invite, the request fails with a `400`. Custom roles cannot be granted via the API. Granting the `workforce` role is also allowed with the `bounty:create` scope.
+Adds a member to an account's team with a system role. Identify them by exactly one of `user_id` or `email`. If the person has not yet accepted — or the email does not belong to a Whop account yet — an invitation is sent instead and the response is `202` with an `object` of `team_member_invite`. If they already have a pending invite, the request fails with a `400`. Granting the `workforce` role is also allowed with the `bounty:create` scope.
 </dd>
 </dl>
 </dd>
@@ -37932,7 +38236,7 @@ client.team_members.create(
 <dl>
 <dd>
 
-**role:** `Whop_sdk::TeamMembers::Types::CreateTeamMembersRequestRole` — The system role to grant. The Partner role can only be granted to the account's attached, verified partner.
+**role:** `Whop_sdk::TeamMembers::Types::CreateTeamMembersRequestRole` — The system role to grant. Custom roles cannot be granted through the API. The Partner role provides view-only access.
     
 </dd>
 </dl>
@@ -37972,7 +38276,7 @@ client.team_members.create(
 <dl>
 <dd>
 
-Retrieves a team member by ID. `email` requires the `company:authorized_user:email:read` scope and is `null` otherwise.
+Retrieves a team member or pending invite by ID.
 </dd>
 </dl>
 </dd>
@@ -38134,7 +38438,7 @@ client.team_members.update(id: "id")
 <dl>
 <dd>
 
-**role:** `Whop_sdk::TeamMembers::Types::UpdateTeamMembersRequestRole` — The system role to grant. The Partner role can only be granted to the account's attached, verified partner.
+**role:** `Whop_sdk::TeamMembers::Types::UpdateTeamMembersRequestRole` — The system role to grant. Custom roles cannot be granted through the API. The Partner role provides view-only access.
     
 </dd>
 </dl>
@@ -38167,7 +38471,7 @@ client.team_members.update(id: "id")
 <dl>
 <dd>
 
-Add funds to a company's platform balance by charging a stored payment method. Top-ups have no fees or taxes and do not count as revenue.
+Add funds to an account's platform balance by charging a stored payment method. Top-ups have no fees or taxes and do not count as revenue.
 
 Required permissions:
  - `payment:charge`
@@ -38388,7 +38692,7 @@ client.trades.list
 <dl>
 <dd>
 
-Creates a trade on the Whop-managed wallet of an account or user and answers `201` with the trade in `pending`. The trade runs in the background; read it with `GET /trades/{id}` until it is `completed`, `failed` or `in_review`. A `buy` bridges `amount` USDT0 to the trading account, sets `leverage` (cross) on `market`, and places one market buy. If the buy does not fill, its money goes back to the wallet. A `close` closes the position in `market`, if one is open, and sends all withdrawable USDC back to the wallet. One trade runs at a time for each wallet. A retry with the same `Idempotency-Key` returns the same trade.
+Places an order, closes a perpetual position, or deposits to or withdraws from the trading balance, from the Whop-managed wallet of an account or user. Answers `201` with the trade in `pending`; it runs in the background, so read it with `GET /trades/:id` until its `status` is `completed`, `failed` or `in_review`. Trades run alongside each other, except a second order on one market at a different leverage, which answers `409`. A retry with the same `Idempotency-Key` returns the same trade.
 </dd>
 </dl>
 </dd>
@@ -38405,8 +38709,7 @@ Creates a trade on the Whop-managed wallet of an account or user and answers `20
 ```ruby
 client.trades.create(
   account_id: "biz_xxxxxxxxxxxxxx",
-  market: "BTC",
-  type: "buy"
+  type: "close"
 )
 ```
 </dd>
@@ -38430,7 +38733,63 @@ client.trades.create(
 <dl>
 <dd>
 
-**amount:** `String` — The USDT0 to send from the wallet for a buy, with at most 6 decimals. Required for a buy.
+**amount:** `String` — Only for a deposit or withdraw, and required for both. For a deposit, the USDT0 to send from the wallet, with at most 6 decimals. For a withdraw, the USDC to send back, at least 1 with at most 6 decimals, or `all`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**client_order_id:** `String` — Only for an order. Your own ID for the trade, 1 to 128 characters, unique for the account. Sending it again with the same order returns the same trade; with a different order it answers `409`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**instrument_type:** `Whop_sdk::Trades::Types::CreateTradesRequestInstrumentType` — `perpetual` or `spot`. Required for an order. Spot needs the trading account in Hyperliquid's unified account mode.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**leverage:** `Integer` — Only for a perpetual order. The cross leverage, from 1 to the market's maximum. Required unless `reduce_only`; not accepted on a reduce-only order.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**market:** `String` — The market: a perpetual such as `BTC`, or for spot a pair priced in USDC such as `HYPE/USDC`. Required for an order or close, and a close takes only a perpetual; not accepted for a deposit or withdraw.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**metadata:** `Internal::Types::Hash[String, String]` — Only for an order. Free-form string-to-string annotations: up to 50 keys of at most 40 characters, values up to 500 characters.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**notional:** `String` — Only for an order. The order value in USD, as a decimal string; the size is rounded down to the market's decimals. Send exactly one of `size` or `notional`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**order_type:** `Whop_sdk::Trades::Types::CreateTradesRequestOrderType` — `market` fills now within `slippage_bps` of the mid price; `limit` fills now at `price` or better. Anything unfilled is canceled. Required for an order.
     
 </dd>
 </dl>
@@ -38438,7 +38797,7 @@ client.trades.create(
 <dl>
 <dd>
 
-**leverage:** `Integer` — The cross leverage for a buy, from 1 to the market's maximum. Required for a buy.
+**price:** `String` — Only for an order. The limit price in USD, as a decimal string Hyperliquid accepts without rounding. Required for a limit order; not accepted for a market order.
     
 </dd>
 </dl>
@@ -38446,7 +38805,7 @@ client.trades.create(
 <dl>
 <dd>
 
-**market:** `String` — The perpetual market, for example `BTC`.
+**reduce_only:** `Internal::Types::Boolean` — Only for a perpetual order. Only reduce an open position; defaults to `false`. A reduce-only order takes no `leverage`.
     
 </dd>
 </dl>
@@ -38454,7 +38813,31 @@ client.trades.create(
 <dl>
 <dd>
 
-**type:** `Whop_sdk::Trades::Types::CreateTradesRequestType` — `buy` or `close`.
+**side:** `Whop_sdk::Trades::Types::CreateTradesRequestSide` — `buy` or `sell`. Required for an order.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**size:** `String` — Only for an order. The size in units of the market, as a decimal string, with at most the market's size decimals. Send exactly one of `size` or `notional`. The order must be worth at least 10 USD, unless reduce-only, and at most 5000 USD.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**slippage_bps:** `Integer` — Only for a market order or a close. The worst price as basis points from the mid price, from 1 to 1000; defaults to 100.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**type:** `Whop_sdk::Trades::Types::CreateTradesRequestType` — `order` places one order from the trading balance, setting cross `leverage` first on a perpetual; when the balance is short, it bridges the USDT0 it needs from the wallet first. `deposit` bridges `amount` USDT0 from the wallet to the trading balance. `withdraw` sends `amount` USDC (or `all`) from the trading balance back to the wallet. `close` closes the whole position in `market` with a market reduce-only order; when the account is then flat, a `withdraw` trade sends the trading balance back to the wallet.
     
 </dd>
 </dl>
@@ -38549,7 +38932,7 @@ client.trades.retrieve(id: "id")
 <dl>
 <dd>
 
-Lists transfers visible to the caller. Optional account filters narrow the results.
+Lists the transfers you can see, sent or received, newest first by default. Optional account filters narrow the results.
 </dd>
 </dl>
 </dd>
@@ -38683,7 +39066,7 @@ client.transfers.list
 <dl>
 <dd>
 
-Moves money between accounts, or into a claim link anyone with the URL can redeem.
+Moves money between Whop balances, sends USDT from an account's wallet, or funds a claim link anyone with the URL can redeem. The `type` you send decides which object comes back.
 </dd>
 </dl>
 </dd>
@@ -38745,7 +39128,7 @@ client.transfers.create
 <dl>
 <dd>
 
-Lists the people and accounts you can send money to.
+Lists the people and accounts you can send money to from a balance. Pass a result's ID as `destination_id` when creating a transfer.
 </dd>
 </dl>
 </dd>
@@ -38894,7 +39277,7 @@ client.transfers.retrieve(id: "id")
 <dl>
 <dd>
 
-Search for users by name or username, ranked by social proximity to the authenticated user. Returns the user's most recently followed users when no query is given.
+Searches for users by name or username, ranked by social proximity to the authenticated user. Without a `query`, returns the user's most recently followed users.
 </dd>
 </dl>
 </dd>
@@ -38988,7 +39371,7 @@ client.users.list
 <dl>
 <dd>
 
-Retrieves the authenticated user — the self view of the user object. Same shape as `GET /users/{id}`, with the self-only fields populated: `email` (email-read scope), `staff` (Whop staff only, staff-read scope), `balance`, `cards` and `earnings_usd` (balance-read scope), the opt-in `balance_history`, and every linked social account.
+Retrieves the authenticated user. Same as `GET /users/:id` with the reserved id `me`: the self view, where self-only fields such as `email`, `balance`, and `cards` can be populated.
 </dd>
 </dl>
 </dd>
@@ -39106,7 +39489,7 @@ client.users.me
 <dl>
 <dd>
 
-Updates the authenticated user's global profile, or their profile override for an account when account_id is given. Not available to API keys.
+Updates the authenticated user's global profile, or their profile override for an account when `account_id` is given. Not available to API keys.
 </dd>
 </dl>
 </dd>
@@ -39208,7 +39591,7 @@ client.users.update_me
 <dl>
 <dd>
 
-Retrieves a user by `user_` tag or username, or the authenticated user with the reserved id `me`. Profiles include linked social accounts — reading your own profile returns every linked account, other profiles only what is public on Whop (the primary Discord and the X account). The self-only fields are populated only when the id is `me`: `email` (email-read scope), `staff` (Whop staff only, staff-read scope), `balance` and `earnings_usd` (balance-read scope), and the opt-in `balance_history`. They are always `null` when addressing a user by tag or username.
+Retrieves a user by `user_` tag or username, or the authenticated user with the reserved id `me`. Self-only fields such as `email`, `balance`, and `earnings_usd` are populated only when the id is `me`, and are always `null` when addressing a user by tag or username.
 </dd>
 </dl>
 </dd>
@@ -39334,7 +39717,7 @@ client.users.retrieve(id: "id")
 <dl>
 <dd>
 
-Updates a user, addressed by `user_` tag, username, or the reserved id `me` for the authenticated user. A user token updates their own global profile; an API key updates the user's account-specific profile override (account_id required).
+Updates a user, addressed by `user_` tag, username, or the reserved id `me` for the authenticated user. A user token updates their own global profile; an API key updates the user's profile override for the account in `account_id`.
 </dd>
 </dl>
 </dd>
@@ -39517,7 +39900,7 @@ client.users.check_access(
 <dl>
 <dd>
 
-Lists the recommended actions computed for the user: personal suggestions (e.g. start a business or become an affiliate) pooled with the highest-impact actions across the accounts the user owns. Business actions are tagged with their `account_id`/`account_name`; personal actions leave those `null`. Self-only: `id` must be `me` or the authenticated user's own tag/username.
+Lists the recommended actions computed for the authenticated user: personal suggestions, such as starting a business or becoming an affiliate, pooled with the highest-impact actions across the accounts the user owns. You can only list your own recommended actions.
 </dd>
 </dl>
 </dd>
@@ -39580,7 +39963,7 @@ client.users.recommend_actions(id: "id")
 <dl>
 <dd>
 
-Returns a paginated list of variants. Omit `account_id` and pass `product_ids` to list a product's public buyable variants.
+Lists an account's variants. To list a product's public, buyable variants without authentication, omit `account_id` and pass `product_ids`.
 </dd>
 </dl>
 </dd>
@@ -39770,7 +40153,7 @@ client.variants.list(
 <dl>
 <dd>
 
-Create a new pricing variant for a product. The variant defines the billing interval, price, and availability for customers.
+Creates a pricing variant for a product, defining the billing interval, price, and availability customers buy it with.
 </dd>
 </dl>
 </dd>
@@ -40040,7 +40423,7 @@ client.variants.create
 <dl>
 <dd>
 
-Retrieves the details of an existing variant.
+Retrieves a variant. Requires no authentication; fields that need a permission are `null` for callers without it.
 </dd>
 </dl>
 </dd>
@@ -40131,7 +40514,7 @@ client.variants.retrieve(
 <dl>
 <dd>
 
-Delete a variant from a product. It stops selling immediately; existing memberships on this variant will not be affected.
+Deletes a variant from a product. It stops selling immediately; existing memberships on it are unaffected.
 </dd>
 </dl>
 </dd>
@@ -40193,7 +40576,7 @@ client.variants.delete(id: "id")
 <dl>
 <dd>
 
-Update a variant's pricing, billing interval, visibility, stock, and other settings.
+Updates a variant's pricing, billing interval, visibility, stock, and other settings.
 </dd>
 </dl>
 </dd>
@@ -40479,7 +40862,7 @@ client.variants.update(id: "id")
 <dl>
 <dd>
 
-Previews tax for a variant before checkout, based on the buyer's location.
+Deprecated. Quote tax with `POST /payment_quotes` instead. Previews tax for a variant before checkout, based on the buyer's location.
 </dd>
 </dl>
 </dd>
@@ -40572,7 +40955,7 @@ client.variants.calculate_tax(
 <dl>
 <dd>
 
-Returns verifications for an account, including their status and any required actions.
+Lists the verifications for an account or user, including their status and any required actions.
 </dd>
 </dl>
 </dd>
@@ -40658,7 +41041,7 @@ client.verifications.list
 <dl>
 <dd>
 
-Starts a hosted verification session for an account or user, or returns the active session when one already exists. Any fields you include in the request body are used to prefill the session. Send `documents` (with `document_type`) to instead verify the person from identity documents included in this request — no hosted session involved. Send `share_token` to reuse a verification another Sumsub account has already completed for this person, instead of verifying them again. Send `verification_id` to reuse a verification the signed-in user already completed on Whop. Every mode except `verification_id` is rejected once the account has an `approved` verification — unlink it first to start a new one — while `verification_id` replaces whichever verification of that kind the account currently has.
+Starts a hosted verification session for an account or user, or returns the active session when one already exists; any fields you send prefill it. To skip the hosted session, send `documents` to verify the person from files in this request, `share_token` to reuse a verification another Sumsub account completed, or `verification_id` to reuse one the signed-in user completed on Whop. For a business, `documents` adds company formation documents to the verification and the hosted session collects the rest. Once the account has an `approved` verification, every mode except `verification_id` is rejected — unlink it first to start a new one.
 </dd>
 </dl>
 </dd>
@@ -40736,7 +41119,7 @@ client.verifications.create
 <dl>
 <dd>
 
-Returns verifications for an account, including their status and any required actions.
+Retrieves a verification by ID, including its status and any information or documents still required.
 </dd>
 </dl>
 </dd>
@@ -40872,7 +41255,7 @@ client.verifications.update(
 <dl>
 <dd>
 
-Lists visible waitlist signups. waitlist_entry:read grants the user's own signups; plan:waitlist:read grants signups for authorized seller accounts. With both permissions, returns their union. Account credentials are limited to their account. Filters narrow this set.
+Lists the waitlist signups you can see. `waitlist_entry:read` returns the user's own signups and `plan:waitlist:read` returns signups to the seller accounts they are authorized on; with both, you get both sets. Account credentials see only their own account's signups.
 </dd>
 </dl>
 </dd>
@@ -41022,7 +41405,7 @@ client.waitlist_entries.list
 <dl>
 <dd>
 
-Joins a free waitlist variant as the authenticated user. Requires waitlist_entry:create. Repeated joins return the existing pending entry, or an approved entry with a valid membership. Paid variants are rejected; no payment method is collected and no membership is granted.
+Joins a free waitlist variant as the authenticated user. Requires `waitlist_entry:create`. Joining again returns the existing pending signup, or the approved one while its membership is valid. Paid variants are rejected; joining collects no payment method and grants no membership.
 </dd>
 </dl>
 </dd>
@@ -41100,7 +41483,7 @@ client.waitlist_entries.create(plan_id: "plan_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Queues approval of every pending signup for an account, optionally narrowed to a variant. Requires plan:waitlist:manage. Paid signups may charge saved payment methods. Approval runs asynchronously: list signups with `status` set to `pending` to follow progress, and retrieve a signup to read its outcome. Signups created after this request are excluded.
+Queues approval of every pending signup for an account, optionally narrowed to a variant. Requires `plan:waitlist:manage`. Paid signups may charge saved payment methods. Approval runs asynchronously: list signups with `status` set to `pending` to follow progress, and retrieve a signup to read its outcome. Signups created after this request are excluded.
 </dd>
 </dl>
 </dd>
@@ -41170,7 +41553,7 @@ client.waitlist_entries.approve_all(account_id: "biz_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-Retrieves a signup owned by the caller with waitlist_entry:read, or submitted to an account they can read with plan:waitlist:read.
+Retrieves a signup the caller owns, with `waitlist_entry:read`, or one submitted to an account they can read, with `plan:waitlist:read`.
 </dd>
 </dl>
 </dd>
@@ -41232,7 +41615,7 @@ client.waitlist_entries.retrieve(id: "id")
 <dl>
 <dd>
 
-Queues approval of a pending signup. Requires plan:waitlist:manage on its seller account. Paid signups may charge their saved payment method. Returns the signup's current state; retrieve it to read `status` and `approval_failure_reason` after processing.
+Queues approval of a pending signup. Requires `plan:waitlist:manage` on its seller account. Paid signups may charge their saved payment method. Returns the signup's current state; retrieve it to read `status` and `approval_failure_reason` after processing.
 </dd>
 </dl>
 </dd>
@@ -41294,7 +41677,7 @@ client.waitlist_entries.approve(id: "id")
 <dl>
 <dd>
 
-Withdraws the caller's pending personal signup. Requires waitlist_entry:cancel. Does not cancel an approved membership.
+Withdraws the caller's own pending signup. Requires `waitlist_entry:cancel`. Does not cancel an approved membership.
 </dd>
 </dl>
 </dd>
@@ -41356,7 +41739,7 @@ client.waitlist_entries.cancel(id: "id")
 <dl>
 <dd>
 
-Denies a pending signup. Requires plan:waitlist:manage on its seller account.
+Denies a pending signup. Requires `plan:waitlist:manage` on its seller account.
 </dd>
 </dl>
 </dd>
@@ -41701,7 +42084,7 @@ client.webhooks.retrieve(id: "id")
 <dl>
 <dd>
 
-Permanently deletes a webhook endpoint. Returns `true` on success, matching the legacy proxy response.
+Permanently deletes a webhook endpoint. To stop deliveries without deleting it, set `enabled` to `false` with `PATCH /webhooks/:id`.
 </dd>
 </dl>
 </dd>
@@ -41943,7 +42326,7 @@ client.webhooks.list_deliveries(id: "id")
 <dl>
 <dd>
 
-Re-sends the exact payload of a past delivery to the webhook's current URL and returns the delivery result. By default the replay keeps the original `webhook-id`, so consumers that deduplicate on it can drop events they already processed. Pass `regenerate_id` to re-send under a freshly generated `webhook-id` instead, so a deduplicating consumer processes the replay as a new message. Only available for enabled webhooks on API version v1; deliveries are retained for 30 days.
+Re-sends the exact payload of a past delivery to the webhook's current URL and returns the delivery result. The replay keeps the original `webhook-id` unless you pass `regenerate_id`, so consumers that deduplicate on it can drop events they already processed. Only available for enabled webhooks on API version `v1`; deliveries are retained for 30 days.
 </dd>
 </dl>
 </dd>
@@ -42024,7 +42407,7 @@ client.webhooks.replay_delivery(
 <dl>
 <dd>
 
-Re-sends the webhook's past deliveries within a time window, optionally limited to specific events or to messages whose most recent delivery attempt failed. Fire and forget: nothing about the replay is stored, and each re-send appears as a new entry in the webhook's delivery log. Each matching message is re-sent once, by default with its original `webhook-id`, so consumers that deduplicate are unaffected; pass `regenerate_ids` to re-send under freshly generated ids instead. Only available for enabled webhooks on API version v1; deliveries are retained for 30 days.
+Re-sends the webhook's past deliveries within a time window, optionally limited to specific events or to failed deliveries. Use it to recover events your endpoint missed. The replay runs asynchronously and nothing about it is stored: each re-send appears as a new entry in the webhook's delivery log. Each matching message is re-sent once, with its original `webhook-id` unless you pass `regenerate_ids`. Only available for enabled webhooks on API version `v1`; deliveries are retained for 30 days.
 </dd>
 </dl>
 </dd>
@@ -42203,7 +42586,7 @@ client.webhooks.test(
 <dl>
 <dd>
 
-Retrieves the account's fees: a singleton document keyed by fee, with any markups its platform adds. Connected accounts see their effective rates, with covered payouts shown as zero; pricing provenance and comparisons are null without parent-account access. `adjustable` on each fee says what the caller may change.
+Retrieves the account's fees as a single document keyed by fee, with any markups its platform adds. Connected accounts see the rates in effect for them. `adjustable` on each fee says what you may change with Update Account Fees.
 </dd>
 </dl>
 </dd>
@@ -42265,7 +42648,7 @@ client.accounts.fees.retrieve(account_id: "account_id")
 <dl>
 <dd>
 
-Updates the account's fees. The response shows effective rates and hides pricing provenance and comparisons without parent-account access. Each key present in the body is replaced; omitted keys are left untouched. Only fees the document reports as `adjustable` can be changed.
+Updates the account's fees. Each key present in the body is replaced; omitted keys are left untouched. Only fees that Retrieve Account Fees reports as `adjustable` can be changed.
 </dd>
 </dl>
 </dd>
@@ -42568,7 +42951,7 @@ client.accounts.fees.update(account_id: "account_id")
 <dl>
 <dd>
 
-Lists payment-financing applications for the account in the URL. Account credentials can access their own account and direct sub-accounts, excluding deeper descendants. User credentials require the read permission on each account. Filters only narrow this visibility.
+Lists payment-financing applications for an account. Account credentials can list their own account and its direct connected accounts, but not deeper descendants; user credentials need read access to the account.
 </dd>
 </dl>
 </dd>
@@ -42598,7 +42981,7 @@ client.accounts.financing_applications.list(account_id: "account_id")
 <dl>
 <dd>
 
-**account_id:** `String` — Merchant account ID, prefixed biz_.
+**account_id:** `String` — Merchant account ID, prefixed `biz_`.
     
 </dd>
 </dl>
@@ -42702,7 +43085,7 @@ client.accounts.financing_applications.list(account_id: "account_id")
 <dl>
 <dd>
 
-Creates an application for merchant payment-financing approval. Requires an existing ledger account. Returns an existing application collecting information or awaiting review; applications awaiting review take precedence. Restricted industries cannot apply. Closed applications allow reapplication. This does not submit the application for review. Supports Idempotency-Key replay; open applications are also reused across different keys.
+Starts an application for payment-financing approval, or returns the account's open one: an application in `awaiting_review` takes precedence over one in `requires_collection`, and the open application is reused across different `Idempotency-Key` values. Creating an application does not submit it for review. The account must have a Whop balance set up, and accounts in restricted industries cannot apply. Once an application closes, the account can apply again.
 </dd>
 </dl>
 </dd>
@@ -42732,7 +43115,7 @@ client.accounts.financing_applications.create(account_id: "account_id")
 <dl>
 <dd>
 
-**account_id:** `String` — Merchant account ID, prefixed biz_.
+**account_id:** `String` — Merchant account ID, prefixed `biz_`.
     
 </dd>
 </dl>
@@ -42764,7 +43147,7 @@ client.accounts.financing_applications.create(account_id: "account_id")
 <dl>
 <dd>
 
-Retrieves a payment-financing application's review state, requirements, saved answers, documents, current terms, and public review feedback. Requires read access to its owning account. Internal review notes and risk metrics are not exposed.
+Retrieves a payment-financing application with its review state, requirements, saved answers, documents, current terms, and review feedback. Requires read access to the account that owns it.
 </dd>
 </dl>
 </dd>
@@ -42797,7 +43180,7 @@ client.accounts.financing_applications.retrieve(
 <dl>
 <dd>
 
-**account_id:** `String` — Merchant account ID, prefixed biz_.
+**account_id:** `String` — Merchant account ID, prefixed `biz_`.
     
 </dd>
 </dl>
@@ -42805,7 +43188,7 @@ client.accounts.financing_applications.retrieve(
 <dl>
 <dd>
 
-**id:** `String` — Financing application ID, prefixed inrq_.
+**id:** `String` — Financing application ID, prefixed `inrq_`.
     
 </dd>
 </dl>
@@ -42837,7 +43220,7 @@ client.accounts.financing_applications.retrieve(
 <dl>
 <dd>
 
-Saves merchant answers while the application requires_collection. The entire batch is atomic. Omitted requirements and answer fields are unchanged; empty arrays clear values or documents, and null money clears a price. Only merchant requirement IDs returned by this application are accepted. Upload documents through the Files API first: new files must belong to the caller, be ready and private, and satisfy the requirement's formats and 20 MB limit. file_ids replaces the requirement's attachments. This does not submit the application.
+Saves merchant answers to an application in `requires_collection`. The batch is atomic: if any answer is rejected, none are saved. Omitted requirements and answer fields are left unchanged. Saving answers does not submit the application; call Submit Financing Application when it is complete.
 </dd>
 </dl>
 </dd>
@@ -42873,7 +43256,7 @@ client.accounts.financing_applications.update(
 <dl>
 <dd>
 
-**account_id:** `String` — Merchant account ID, prefixed biz_.
+**account_id:** `String` — Merchant account ID, prefixed `biz_`.
     
 </dd>
 </dl>
@@ -42881,7 +43264,7 @@ client.accounts.financing_applications.update(
 <dl>
 <dd>
 
-**id:** `String` — Financing application ID, prefixed inrq_.
+**id:** `String` — Financing application ID, prefixed `inrq_`.
     
 </dd>
 </dl>
@@ -42921,7 +43304,7 @@ client.accounts.financing_applications.update(
 <dl>
 <dd>
 
-Submits a complete application for financing review. Present the application's terms.content, policies, and disclosure to the merchant and collect affirmative acceptance before calling this endpoint. Pass the terms.version that was presented; stale versions are rejected. The server records acceptance, submitting actor, and submission time before entering awaiting_review. Only requires_collection applications may submit, including after a reviewer requests more information. Resubmissions require acceptance again. Use Idempotency-Key for retries; submitting an application already in review without replay returns an error. Approval does not itself enable financing payment methods.
+Submits a complete application for financing review, recording the merchant's acceptance, who submitted, and when, then moving it to `awaiting_review`. Before calling, present the application's `terms.content`, policies, and disclosure to the merchant and collect affirmative acceptance; every resubmission needs acceptance again. Only an application in `requires_collection` can be submitted, including after a reviewer requests more information. Retry with the same `Idempotency-Key`: submitting an application already in review without a replay returns an error. Approval does not by itself enable financing payment methods.
 </dd>
 </dl>
 </dd>
@@ -42958,7 +43341,7 @@ client.accounts.financing_applications.submit(
 <dl>
 <dd>
 
-**account_id:** `String` — Merchant account ID, prefixed biz_.
+**account_id:** `String` — Merchant account ID, prefixed `biz_`.
     
 </dd>
 </dl>
@@ -42966,7 +43349,7 @@ client.accounts.financing_applications.submit(
 <dl>
 <dd>
 
-**id:** `String` — Financing application ID, prefixed inrq_.
+**id:** `String` — Financing application ID, prefixed `inrq_`.
     
 </dd>
 </dl>
@@ -43079,6 +43462,7 @@ Required scopes depend on the preferences being updated:
 | `cards_auto_top_up`, `cards_notifications` | `payout:account:update` |
 | `dispute_fighter_enabled` | `payment:dispute` |
 | `economic_intelligence_duration_key`, `economic_intelligence_auto_renew` | `company:update` |
+| `feedback_options` | `company:manage_checkout` |
 
 When updating preferences from multiple rows, all corresponding scopes are required for the account.
 </dd>
@@ -43198,6 +43582,14 @@ client.accounts.preferences.update(account_id: "account_id")
 <dl>
 <dd>
 
+**feedback_options:** `Internal::Types::Array[Whop_sdk::Accounts::Preferences::Types::UpdatePreferencesRequestFeedbackOptionsItem]` — Replaces the account's own cancel reasons, shown to members in this order when they cancel. Pass an option's `id` to keep it, for example when renaming it; options without an `id` are added, and options left out are removed. Pass an empty array to go back to Whop's default reasons. Members who already picked an option keep the label they saw. Requires the `company:manage_checkout` scope on your API key.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **preferred_settlement_currency:** `Whop_sdk::Accounts::Preferences::Types::UpdatePreferencesRequestPreferredSettlementCurrency` — Settle every new sale into this currency, regardless of the plan's currency or what the buyer paid in; sales converted this way carry an additional 0.5% FX fee. Pass `null` to go back to settling each sale in its plan's currency. Changing it never converts money already in your balances, and it can change at most once every 7 days (see `preferred_settlement_currency_changeable_at`). Requires the `payout:account:update` scope on your API key.
     
 </dd>
@@ -44374,7 +44766,7 @@ client.external_accounts.posts.list(
 <dl>
 <dd>
 
-Returns the top entities behind one high-level financial report bucket and an aggregate remainder.
+Breaks one bucket of a financial report, such as payments received or card spend, into the customers, accounts, merchants, or campaigns that contributed most, with the rest summed as a remainder. Use it to explain a total from `GET /financial_reports`.
 </dd>
 </dl>
 </dd>
@@ -44500,7 +44892,7 @@ client.financial_reports.breakdown.retrieve(
 <dl>
 <dd>
 
-Lists activity for a member and all of their non-drafted memberships, most recent first.
+Lists activity for a member and all of their memberships that are not `drafted`, most recent first.
 </dd>
 </dl>
 </dd>
@@ -44578,6 +44970,174 @@ client.members.logs.list(id: "id")
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+## Members Notes
+<details><summary><code>client.members.notes.<a href="/lib/whop_sdk/members/notes/client.rb">list</a>(member_id:) -> Whop_sdk::Members::Notes::Types::ListNotesResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Lists a member's notes, newest first. Notes are visible to the account's team.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.members.notes.list(member_id: "member_id")
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**member_id:** `String` — The member the notes are about, prefixed `mber_`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**first:** `Integer` — Number of results to return from the start of the range.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**after:** `String` — Return results after this cursor. Use `page_info.end_cursor` from the previous response to fetch the next page.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**last:** `Integer` — Number of results to return from the end of the range.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**before:** `String` — Return results before this cursor. Use `page_info.start_cursor` from the previous response to fetch the previous page.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::Members::Notes::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.members.notes.<a href="/lib/whop_sdk/members/notes/client.rb">create</a>(member_id:, request) -> Whop_sdk::Types::MemberNote</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Adds a note to a member. Notes are visible to the account's team.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.members.notes.create(
+  member_id: "member_id",
+  content: "Wants a call next week."
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**member_id:** `String` — The member the notes are about, prefixed `mber_`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**content:** `String` — The note text.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::Members::Notes::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>
@@ -44712,6 +45272,14 @@ client.partners.businesses.list
 <dl>
 <dd>
 
+**advance_status:** `Whop_sdk::Partners::Businesses::Types::ListBusinessesRequestAdvanceStatus` — Filter the authenticated partner's CPA offers by status. Use offered for every state after qualification.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **status:** `Whop_sdk::Partners::Businesses::Types::ListBusinessesRequestStatus` — Filter by referral status.
     
 </dd>
@@ -44894,6 +45462,188 @@ client.partners.businesses.retrieve(id: "id")
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.partners.businesses.<a href="/lib/whop_sdk/partners/businesses/client.rb">update</a>(id:, request) -> Whop_sdk::Partners::Businesses::Types::UpdateBusinessesResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Save annual projections for a business referred by the authenticated partner. Projections cannot be changed after saving; repeating the same values is allowed. Public API access requires a partner OAuth token; business API keys are not supported.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.partners.businesses.update(
+  id: "id",
+  annual_ads_usd: "120000",
+  annual_processing_usd: "1200000"
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**id:** `String` — The partner business ID (a coma_ identifier).
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**annual_ads_usd:** `String` — Annual projected Whop Ads spend in USD.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**annual_processing_usd:** `String` — Annual projected processing on Whop in USD.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::Partners::Businesses::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.partners.businesses.<a href="/lib/whop_sdk/partners/businesses/client.rb">accept_commission_advance</a>(id:, request) -> Whop_sdk::Partners::Businesses::Types::AcceptCommissionAdvanceBusinessesResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Accept the authenticated partner's CPA offer with the reviewed terms and signed offer token. Public API access requires a partner OAuth token; business API keys are not supported.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.partners.businesses.accept_commission_advance(
+  id: "id",
+  acknowledgments: %w[commission_replacement clawback term],
+  expected_amount_usd: "1439.99",
+  offer_token: "eyJfcmFpbHMiOnsiZGF0YSI6MSwicHVyIjoiYmxvYl9pZCJ9fQ==--xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
+  terms_version: "2026-01-01"
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**id:** `String` — The referred business relationship ID.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**acknowledgments:** `Internal::Types::Array[Whop_sdk::Partners::Businesses::Types::AcceptCommissionAdvanceBusinessesRequestAcknowledgmentsItem]` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**expected_amount_usd:** `String` — Reviewed payment amount in USD.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**offer_token:** `String` — Signed offer token returned by the partner business response. Requires partner:commission_advance:accept permission to retrieve.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**terms_version:** `String` — Reviewed CPA terms version.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::Partners::Businesses::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>
@@ -45054,7 +45804,7 @@ client.partners.businesses.earnings.list(id: "id")
 <dl>
 <dd>
 
-Charges a buyer for a variant from card details the caller holds itself, for integrators whose own systems are PCI compliant. Card details are accepted only on the vault host, where the card is tokenized before it reaches Whop; the official SDKs route this operation there, and raw card details sent to the regular host are refused. (Whop's own clients, which tokenize with the Basis Theory SDK, send the resulting token intent id to the regular host.) Collection runs in the background: the response is the payment as created, not its outcome — poll Retrieve status for how far it has got and what the buyer must still do, such as 3D Secure.
+Charges a buyer for a variant from card details you hold yourself, for integrators whose own systems are PCI compliant. Card details are accepted only on the vault host, which tokenizes the card before it reaches Whop; the official SDKs route this operation there, and raw card details sent to the regular host are refused. Collection runs in the background, so the response is the payment as created, not its outcome: poll Retrieve payment status for how far it has got and what the buyer must still do, such as 3D Secure.
 </dd>
 </dl>
 </dd>
@@ -45129,6 +45879,14 @@ client.payments.direct.create(
 <dl>
 <dd>
 
+**line_items:** `Internal::Types::Array[Whop_sdk::Payments::Direct::Types::CreateDirectRequestLineItemsItem]` — What the buyer is purchasing. Each entry names an existing variant by plan_id. Several entries form a cart, which requires every variant to be compatible, belong to this account, and use the same currency.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **member_id:** `String` — The member to charge, prefixed `mber_`. When omitted the buyer is resolved from `billing_details.email`.
     
 </dd>
@@ -45161,7 +45919,7 @@ client.payments.direct.create(
 <dl>
 <dd>
 
-**quote_id:** `String` — A payment quote from `POST /payment_quotes`, prefixed `pq_`. The payment charges exactly the quote: its purchase (its variants and quantities, or the `plan` it priced), which this body may then omit, its promo code, and its tax, the quote's `tax_amount` rather than a figure calculated now. Omit it, or send null, to have tax calculated when the payment is charged. The quote must belong to `account_id`. A purchase field you omit or send as null takes the quote's value; the buyer's email, the addresses and the payment method are this request's own, never the quote's. Whatever you do send must describe the quoted purchase: the same variants, quantities and promo code. A quote that priced `plan` takes only the same `plan` you sent to `POST /payment_quotes` (or omit the purchase to take the quoted one), never `plan_id` or `line_items`, and a quote that priced variants by id never takes `plan`. Unless the quote located no buyer (`located_by` is null), the address the payment carries (its shipping address, else its billing address) must put the buyer where the quote priced tax, by country, state and postal code; otherwise the payment is refused with 400 before the payment method is used. A quote located by IP address or by the country the buyer chose (`located_by` is `ip_address` or `presentment_country`) is a preview and cannot be paid. A quote is consumed by one payment: a declined payment keeps it and can be retried; a new payment needs a new quote. A quote cannot be charged through PayPal; such a payment is refused before the payment method is used. A quote priced in a `presentment_currency` is charged in that currency at the quote's `exchange_rate`. A payment refused over its quote carries an error `code`. `quote_expired`: the quote has expired; quote again. `quote_tax_unavailable`: the quote could not price tax; quote again, or omit `quote_id`. `quote_preview_only`: the quote was located by IP address or by the country the buyer chose; quote again with the buyer's address. `quote_in_use` (409): another payment holds the quote. `quote_mismatch`: the purchase or the buyer's address is not the one quoted. `quote_rate_expired`: the exchange rate the quote was priced at has moved too far to charge; quote again. `payment_method_currency_unsupported`: the payment method cannot pay in the quote's currency; use another method, or quote again in another currency. `quote_processor_unsupported`: the payment method cannot pay a quote, as with PayPal; use another method, or omit `quote_id` to have tax calculated when the payment is charged.
+**quote_id:** `String` — A payment quote from `POST /payment_quotes`, prefixed `pq_`. The payment charges exactly the quote: its purchase (its variants and quantities, or the `plan` it priced), which this body may then omit, its promo code, and its tax, the quote's `tax_amount` rather than a figure calculated now. Omit it, or send null, to have tax calculated when the payment is charged. The quote must belong to `account_id`. A purchase field you omit or send as null takes the quote's value; the buyer's email, the addresses and the payment method are this request's own, never the quote's. Whatever you do send must describe the quoted purchase: the same variants, quantities and promo code. A quote that priced `plan` takes only the same `plan` you sent to `POST /payment_quotes` (or omit the purchase to take the quoted one), never `plan_id` or `line_items`, and a quote that priced variants by id never takes `plan`. Unless the quote located no buyer (`located_by` is null), the address the payment carries (its shipping address, else its billing address) must put the buyer where the quote priced tax, by country, state and postal code; otherwise the payment is refused with 400 before the payment method is used. A quote located by IP address or by the country the buyer chose (`located_by` is `ip_address` or `presentment_country`) is a preview and cannot be paid. A quote is consumed by one payment: a declined payment keeps it and can be retried; a new payment needs a new quote. A quote cannot be charged by a processor that doesn't take quotes, such as a seller's own connected PayPal account; such a payment is refused before the payment method is used. A quote priced in a `presentment_currency` is charged in that currency at the quote's `exchange_rate`. A payment refused over its quote carries an error `code`. `quote_expired`: the quote has expired; quote again. `quote_tax_unavailable`: the quote could not price tax; quote again, or omit `quote_id`. `quote_preview_only`: the quote was located by IP address or by the country the buyer chose; quote again with the buyer's address. `quote_in_use` (409): another payment holds the quote. `quote_mismatch`: the purchase or the buyer's address is not the one quoted. `quote_rate_expired`: the exchange rate the quote was priced at has moved too far to charge; quote again. `payment_method_currency_unsupported`: the payment method cannot pay in the quote's currency; use another method, or quote again in another currency. `quote_processor_unsupported`: the payment would be processed by a processor that doesn't take quotes, such as a seller's own connected PayPal account; use another method, or omit `quote_id` to have tax calculated when the payment is charged.
     
 </dd>
 </dl>
@@ -45360,7 +46118,7 @@ client.payouts.methods.list
 <dl>
 <dd>
 
-Saves a new place an account or user can pay out to. Sensitive details are vaulted in transit and never stored raw.
+Saves a bank account, wallet, or crypto address an account or user can pay out to, from a method listed by `GET /payouts/supported_methods`. Sensitive details are vaulted in transit and never stored raw.
 </dd>
 </dl>
 </dd>
@@ -45430,6 +46188,14 @@ client.payouts.methods.create(supported_payout_method_id: "podst_xxxxxxxxxxxxxx"
 <dl>
 <dd>
 
+**paypal_link_token:** `String` — The token your `return_url` received after a Log in with PayPal session started with `POST /payouts/paypal_link_sessions`. Use it for a PayPal supported payout method instead of `fields`. Sending `fields` or `plaid_public_token` alongside it is rejected, and `nickname` is ignored because Whop names the method after the PayPal email. The PayPal holder's name must match the name on the account's payout setup. An account PayPal reports as unverified, or with an unconfirmed email, is saved and flagged on the method's log rather than refused. Single use; expires 15 minutes after the login.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **recipient:** `Whop_sdk::Payouts::Methods::Types::CreateMethodsRequestRecipient` — Creates a recipient payout account linked to the funding ledger as a non-default account, then saves the bank method on it. No Whop user, company, or recipient ledger is created. A valid recipient email is required. Recipient methods cannot be default or recurring methods and cannot use Plaid.
     
 </dd>
@@ -45602,6 +46368,104 @@ client.payouts.methods.update(id: "id")
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+## Payouts PaypalLinkSessions
+<details><summary><code>client.payouts.paypal_link_sessions.<a href="/lib/whop_sdk/payouts/paypal_link_sessions/client.rb">create</a>(request) -> Whop_sdk::Payouts::PaypalLinkSessions::Types::CreatePaypalLinkSessionsResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Starts a Log in with PayPal session so PayPal itself can confirm the account holder owns a verified PayPal account. Send the holder to `authorize_url`; after they log in, PayPal returns them to Whop, and Whop redirects the browser to your `return_url` with a `paypal_link_token` query parameter to pass to `POST /payouts/methods`. If the login fails or is canceled, `return_url` receives an `error` query parameter (`paypal_login_canceled` or `paypal_login_failed`) instead. The payout method saved this way pays the email on the PayPal account, and its holder name must match the name on the account's payout setup. PayPal login is rolling out per account: until it is enabled for the account this answers `403 forbidden`, and `supports_paypal_login` on `GET /payouts/supported_methods` is false.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.payouts.paypal_link_sessions.create(
+  return_url: "https://example.com/settings/payouts",
+  supported_payout_method_id: "podst_xxxxxxxxxxxxxx"
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**account_id:** `String` — The account that will own the PayPal payout method, prefixed `biz_`. Provide this or `user_id`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**destination_currency:** `String` — Currency the PayPal payout method will deliver payouts in.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**return_url:** `String` — Where to send the holder once the PayPal login finishes. Must be an `https` URL; it receives `paypal_link_token` on success or `error` on failure.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**supported_payout_method_id:** `String` — The PayPal supported payout method to connect (a `podst_` identifier whose `supports_paypal_login` is true).
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**user_id:** `String` — The user who will own the PayPal payout method, prefixed `user_`. Provide this or `account_id`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::Payouts::PaypalLinkSessions::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>
@@ -45619,7 +46483,7 @@ client.payouts.methods.update(id: "id")
 <dl>
 <dd>
 
-Lists the payout methods an account or user is eligible to add.
+Lists the payout methods an account or user is eligible to add. Pass a result's ID as `supported_payout_method_id` to `POST /payouts/methods` to save one.
 </dd>
 </dl>
 </dd>
@@ -45762,7 +46626,7 @@ client.payouts.supported_methods.list
 <dl>
 <dd>
 
-Saves a card for later charges from card details the caller holds itself, for integrators whose own systems are PCI compliant. Card details are accepted only on the vault host, where the card is tokenized before it reaches Whop; the official SDKs route this operation there, and raw card details sent to the regular host are refused. (Whop's own clients, which tokenize with the Basis Theory SDK, send the resulting token intent id to the regular host.) The setup runs in the background: poll Retrieve setup status for its outcome and for anything the buyer must still do, such as 3D Secure. Once it succeeds, the saved payment method arrives on the `setup_intent.succeeded` webhook and in List payment methods for the member.
+Saves a card for later charges from card details you hold yourself, for integrators whose own systems are PCI compliant. Send this operation to the vault host, which tokenizes the card before it reaches Whop; the official SDKs route it there, and raw card details sent to the regular host are refused. The setup runs in the background: poll Retrieve setup status for its outcome and for anything the buyer must still do, such as 3D Secure. Once it succeeds, the saved payment method arrives on the `setup_intent.succeeded` webhook and in List payment methods for the member.
 </dd>
 </dl>
 </dd>
@@ -45886,7 +46750,7 @@ client.setup_intents.direct.create(
 <dl>
 <dd>
 
-Lists every report: the aggregates that are not bucketed over time. Each entry names the report's path, its window kind, the breakdowns it accepts and its columns. A property column is an attribute of the row and lists the breakdowns it can ride along with. A metric column is a number measured over the row, with the unit that sets its JSON type, the aggregate that says how to combine it across rows, and the breakdowns and windows it supports. For a bucketed series, use `GET /stats/time_series`.
+Lists every report: the aggregates that are not bucketed over time, with the breakdowns and columns each one accepts. Use it to discover what a report can return before you retrieve it. For a bucketed series, use `GET /stats/time_series`.
 </dd>
 </dl>
 </dd>
@@ -45940,7 +46804,7 @@ client.stats.reports.list
 <dl>
 <dd>
 
-Payments across all of Whop, for up to four windows at once. Break rows down by business type, industry type, account country or customer country, and let the business type ride along on industry type rows. The report covers the whole platform, so it takes no `account_id` and any authenticated caller can read it. A breakdown value with fewer than three businesses behind it is left out, and a filtered total that small comes back with every metric `null`.
+Retrieves payments across all of Whop for up to four windows at once, optionally broken down by business type, industry type, account country or customer country. The report covers the whole platform, so it takes no `account_id` and any authenticated caller can read it.
 </dd>
 </dl>
 </dd>
@@ -45978,7 +46842,7 @@ client.stats.reports.platform_trends
 <dl>
 <dd>
 
-**columns:** `String` — Comma-separated properties and metrics to return on each row. Defaults to `gross_revenue,businesses`.
+**columns:** `String` — Comma-separated properties and metrics to return on each row. `business_type` can ride along on `industry_type` rows. Defaults to `gross_revenue,businesses`.
     
 </dd>
 </dl>
@@ -46153,7 +47017,7 @@ client.stats.time_series.list
 <dl>
 <dd>
 
-Retrieves a metric as a time series of points for an account or user over a time range. For an aggregate that is not bucketed over time, use a report from `GET /stats/reports`. The `market_prices` metric is public and requires no authentication. The `funnel` metric measures 2 to 10 ordered events per person. Its first matching event inside from/to anchors the cohort, breakdown and conversion window; later entries do not restart it. Intervening events are allowed, and conversions may occur after to. Funnel values are final conversion percentages; steps include counts and cumulative conversion percentages. Experiment funnels use experiment.exposure as step 1 and breakdown_by=variant. Pass steps using bracket parameters such as steps[1][event]=pixel.page&steps[1][page]=/pricing*&steps[2][event]=payment.completed.
+Retrieves a metric as a series of points over a time range for an account or user. For an aggregate that is not bucketed over time, use a report from `GET /stats/reports`. The `market_prices` metric is public and requires no authentication.
 </dd>
 </dl>
 </dd>
@@ -46510,7 +47374,7 @@ client.stats.time_series.retrieve(
 <dl>
 <dd>
 
-**steps:** `Whop_sdk::Types::RetrieveTimeSeriesRequestSteps` — Funnel only. Required when metric=funnel. Consecutive one-based steps encoded as steps[1][event], steps[1][page], steps[2][event], and so on. Values are scalar strings, never JSON.
+**steps:** `Whop_sdk::Types::RetrieveTimeSeriesRequestSteps` — Funnel only. Required when metric=funnel. 2 to 10 ordered events per person, as consecutive one-based bracket parameters such as `steps[1][event]=pixel.page&steps[1][page]=/pricing*&steps[2][event]=payment.completed`. Values are scalar strings, never JSON. A person's first step 1 match inside `from`/`to` anchors their cohort, breakdown, and conversion window; later matches do not restart it. Other events may occur between steps, and conversions may land after `to`. For an experiment funnel, make `experiment.exposure` step 1 and pass `breakdown_by=variant`.
     
 </dd>
 </dl>
@@ -46783,7 +47647,7 @@ client.stats.time_series.retrieve(
 <dl>
 <dd>
 
-Lists the authenticated user's own OAuth grants — one per app they have authorized, per account they authorized it for. The list is always the caller's own; there is no parameter for reading another user's grants. Requires a user session: an API key or an OAuth token is refused, so an app can never enumerate the other apps a user has authorized.
+Lists the authenticated user's own OAuth grants: one per app they have authorized, per account they authorized it for. You cannot read another user's grants. Requires a user session: an API key or an OAuth token is refused, so an app can never enumerate the other apps a user has authorized.
 </dd>
 </dl>
 </dd>
@@ -46893,7 +47757,7 @@ client.users.oauth_grants.list
 <dl>
 <dd>
 
-Completes the OAuth authorization step for the authenticated user: records their consent for the scopes an app asked for and mints the authorization code to hand back to it. Returns the grant, plus a `redirect_url` carrying that code — the one and only time it is returned. Exchange the code at `POST /oauth/token` with the verifier for `code_challenge`, or with the app's secret when a confidential app sent none. Requires a user session, because consent has to come from the account holder: an API key or an OAuth token is refused, so an app can never authorize itself. Send an `Idempotency-Key` to make a retry safe — a replay returns the original `redirect_url` and its code rather than issuing a second one.
+Completes the OAuth authorization step for the authenticated user: records their consent to the scopes an app asked for and mints an authorization code. Returns the grant plus a `redirect_url` carrying the code, which is returned only this once; the app exchanges it at `POST /oauth/token`. Requires a user session, because consent has to come from the account holder: an API key or an OAuth token is refused, so an app can never authorize itself. Send an `Idempotency-Key` so a retry returns the original `redirect_url` and code instead of issuing a second one.
 </dd>
 </dl>
 </dd>
@@ -47040,7 +47904,7 @@ client.users.oauth_grants.create(
 <dl>
 <dd>
 
-Lists the authenticated user's own passkeys, newest first. The list is always the caller's own; there is no parameter for reading another user's passkeys. Requires a user session: an API key or an OAuth token is refused, because a passkey confirms the account holder before a sensitive action and no app may enumerate one.
+Lists the authenticated user's own passkeys, newest first. You cannot read another user's passkeys. Requires a user session: an API key or an OAuth token is refused, because a passkey confirms the account holder before a sensitive action and no app may enumerate one.
 </dd>
 </dl>
 </dd>
@@ -47395,7 +48259,7 @@ client.users.passkeys.delete(
 <dl>
 <dd>
 
-Retrieves the authenticated user's settings document. Addressed only as `me` — the document always belongs to the session user.
+Retrieves the authenticated user's settings document.
 </dd>
 </dl>
 </dd>
@@ -47536,13 +48400,7 @@ client.users.preferences.update
 <dl>
 <dd>
 
-Sets the authenticated user's notification preferences. Each preference is addressed by `scope`, not by id, so a scope read back from either list endpoint can be sent straight here.
-
-A scope naming an experience with no topic sets that experience's level, and accepts all three levels. Any other scope sets a topic override, which is binary — `all` or `nothing`. A topic override with no `channel` applies to every delivery channel.
-
-`level: null` clears the preference. Preferences are stored as overrides, so clearing one means the scope inherits its default again rather than being switched off.
-
-The batch is applied in one transaction: if any entry is rejected, none are written. Experience levels are applied before topic overrides, because setting a level replaces every topic preference for that experience — so an override sent alongside a level wins. The response reports what each scope now resolves to, in the order the entries were sent.
+Sets the authenticated user's notification preferences, each addressed by `scope` rather than by ID. The batch is applied in one transaction: if any entry is rejected, none are written. Experience levels are applied before topic overrides, because setting a level replaces every topic preference for that experience, so an override sent alongside a level wins. The response reports what each scope now resolves to, in the order the entries were sent.
 </dd>
 </dl>
 </dd>
@@ -47678,7 +48536,7 @@ client.users.preferences.notifications.experiences.list
 <dl>
 <dd>
 
-Lists the authenticated user's topic-scoped notification preferences, plus user-agnostic platform defaults. Each filter matches preferences scoped to its value or not narrowed on that dimension. Per-experience levels are listed separately, by `GET /users/me/preferences/notifications/experiences`.
+Lists the authenticated user's topic-scoped notification preferences, plus user-agnostic platform defaults. Per-experience levels are listed separately, by `GET /users/me/preferences/notifications/experiences`.
 </dd>
 </dl>
 </dd>
@@ -47716,7 +48574,7 @@ client.users.preferences.notifications.topics.list
 <dl>
 <dd>
 
-**account_id:** `String` — Only return preferences scoped to this account's member notifications (`biz_` tag).
+**account_id:** `String` — Only return preferences scoped to this account's member notifications (`biz_` tag), or not narrowed to an account.
     
 </dd>
 </dl>
@@ -47724,7 +48582,7 @@ client.users.preferences.notifications.topics.list
 <dl>
 <dd>
 
-**team_account_id:** `String` — Only return preferences scoped to this account's team notifications (`biz_` tag).
+**team_account_id:** `String` — Only return preferences scoped to this account's team notifications (`biz_` tag), or not narrowed to a team account.
     
 </dd>
 </dl>
@@ -47732,7 +48590,7 @@ client.users.preferences.notifications.topics.list
 <dl>
 <dd>
 
-**experience_id:** `String` — Only return preferences scoped to this experience (`exp_` tag).
+**experience_id:** `String` — Only return preferences scoped to this experience (`exp_` tag), or not narrowed to an experience.
     
 </dd>
 </dl>
@@ -47740,7 +48598,7 @@ client.users.preferences.notifications.topics.list
 <dl>
 <dd>
 
-**topic_id:** `String` — Only return preferences scoped to this notification topic (`topic_` tag).
+**topic_id:** `String` — Only return preferences scoped to this notification topic (`topic_` tag), or not narrowed to a topic.
     
 </dd>
 </dl>