whop_sdk 2.5.0 → 2.6.0

data/reference.md

@@ -325,6 +325,14 @@ client.accounts.list
 <dl>
 <dd>
 
+**owner_id:** `String` — Return only accounts owned by this user (`user_...`), the account's `owner`. Cannot be combined with `parent_account_id`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **request_options:** `Whop_sdk::Accounts::RequestOptions` 
     
 </dd>
@@ -529,6 +537,116 @@ client.accounts.me
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.accounts.<a href="/lib/whop_sdk/accounts/client.rb">search</a>() -> Whop_sdk::Accounts::Types::SearchAccountsResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Finds accounts by name among the accounts the credential can list. Support searches cover every company and return only the 50 best matches.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.accounts.search(query: "query")
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<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>
+
+**query:** `String` — The account name to search for.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**order:** `Whop_sdk::Accounts::Types::SearchAccountsRequestOrder` — Sort field. Without it, support searches return the best match first and other searches return the newest account first.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**direction:** `Whop_sdk::Accounts::Types::SearchAccountsRequestDirection` — Sort direction.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::Accounts::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>
@@ -1067,6 +1185,14 @@ client.accounts.update(id: "id")
 <dl>
 <dd>
 
+**whop_partner_enabled:** `Internal::Types::Boolean` — Set to `true` to turn on Whop Partner mode for the account, so its team can refer businesses and the account is paid partner commission on their sales. Recorded once; `false` is rejected.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **industry_type:** `Object` 
     
 </dd>
@@ -1414,7 +1540,7 @@ client.accounts.suspend(id: "id")
 <dl>
 <dd>
 
-Transfers ownership of the account to another user, identified by user ID or email address. If the recipient already holds the owner role, ownership moves immediately; otherwise they get an invite and ownership moves when they accept.
+Transfers ownership of the account to another user, identified by user ID or email address. If the recipient already holds the owner role, ownership moves immediately; otherwise they get an invite and ownership moves when they accept. The Whop CLI and MCP can hand off a business their user owns as a partner (`as_partner: true`) with the `partner:handoff` scope; other OAuth apps cannot transfer ownership.
 </dd>
 </dl>
 </dd>
@@ -1566,7 +1692,7 @@ client.ad_campaigns.list
 <dl>
 <dd>
 
-**order:** `Whop_sdk::AdCampaigns::Types::ListAdCampaignsRequestOrder` — The field to sort by. Defaults to created_at. Stat columns (spend, impressions, …) rank over the stats_from/stats_to window across the whole list, not just the current page. results, cost_per_result and return_on_ad_spend rank by the same Whop pixel-attributed values the response reports.
+**order:** `Whop_sdk::AdCampaigns::Types::ListAdCampaignsRequestOrder` — The field to sort by. Defaults to created_at. Stat columns (spend, impressions, …) rank over the stats_from/stats_to window across the whole list, not just the current page. results, cost_per_result and return_on_ad_spend rank by the same Whop pixel-attributed values the response reports, and link_clicks by the same Whop pixel page views.
     
 </dd>
 </dl>
@@ -3088,7 +3214,7 @@ client.ad_groups.list(ad_campaign_ids: ["adcamp_xxxxxxxxxxxxxx"])
 <dl>
 <dd>
 
-**order:** `Whop_sdk::AdGroups::Types::ListAdGroupsRequestOrder` — The field to sort by. Defaults to created_at. Stat columns (spend, impressions, …) rank over the stats_from/stats_to window across the whole list, not just the current page. results, cost_per_result and return_on_ad_spend rank by the same Whop pixel-attributed values the response reports.
+**order:** `Whop_sdk::AdGroups::Types::ListAdGroupsRequestOrder` — The field to sort by. Defaults to created_at. Stat columns (spend, impressions, …) rank over the stats_from/stats_to window across the whole list, not just the current page. results, cost_per_result and return_on_ad_spend rank by the same Whop pixel-attributed values the response reports, and link_clicks by the same Whop pixel page views.
     
 </dd>
 </dl>
@@ -4839,7 +4965,7 @@ client.ads.list(
 <dl>
 <dd>
 
-**order:** `Whop_sdk::Ads::Types::ListAdsRequestOrder` — The field to sort by. Defaults to created_at. Stat columns (spend, impressions, …) rank over the stats_from/stats_to window across the whole list, not just the current page. results, cost_per_result and return_on_ad_spend rank by the same Whop pixel-attributed values the response reports.
+**order:** `Whop_sdk::Ads::Types::ListAdsRequestOrder` — The field to sort by. Defaults to created_at. Stat columns (spend, impressions, …) rank over the stats_from/stats_to window across the whole list, not just the current page. results, cost_per_result and return_on_ad_spend rank by the same Whop pixel-attributed values the response reports, and link_clicks by the same Whop pixel page views.
     
 </dd>
 </dl>
@@ -14664,7 +14790,7 @@ client.courses.update(id: "cors_xxxxxxxxxxxxx")
 <dl>
 <dd>
 
-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.
+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. Pass `payment_method_id` to also charge a business's saved payment method for `amount` in USD and add it to the business's balance; that requires authentication with the `payment:charge` scope. The charge has no fees or taxes and does not count as revenue.
 </dd>
 </dl>
 </dd>
@@ -14694,7 +14820,7 @@ client.deposits.create(destination: "biz_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
-**amount:** `Integer` — Amount to prefill on hosted deposit page. Crypto deposits require a $10 minimum.
+**amount:** `Integer` — Amount to prefill on hosted deposit page. Crypto deposits require a $10 minimum. With `payment_method_id`, the amount in USD to charge, and required.
     
 </dd>
 </dl>
@@ -14710,6 +14836,14 @@ client.deposits.create(destination: "biz_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
+**payment_method_id:** `String` — A saved payment method of the business to charge for `amount`, prefixed `payt_`. Save one with Create setup intent and `owner_id` set to the account. Only for a `biz_` destination, and requires authentication with the `payment:charge` scope. A declined charge fails the request with 400.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **request_options:** `Whop_sdk::Deposits::RequestOptions` 
     
 </dd>
@@ -15300,6 +15434,68 @@ client.disputes.update(id: "id")
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.disputes.<a href="/lib/whop_sdk/disputes/client.rb">accept</a>(id:) -> Whop_sdk::Types::Dispute</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Accepts a chargeback, conceding it to the customer instead of contesting it. The payment processor closes the dispute as `lost`. This is final — the dispute cannot be contested afterwards. Only a dispute whose `acceptable` is true can be accepted.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.disputes.accept(id: "id")
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**id:** `String` — The dispute ID (`dspt_` tag).
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::Disputes::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>
@@ -19748,7 +19944,7 @@ client.external_accounts.connect(
 <dl>
 <dd>
 
-**platform:** `Whop_sdk::ExternalAccounts::Types::ConnectExternalAccountsRequestPlatform` — The platform to connect the external account on. Use `meta_business` to connect Meta Business assets, which is how Facebook Pages and Instagram accounts are connected — there is no separate `instagram` value. Use `tiktok` for TikTok accounts, `snapchat` for Snapchat Public Profiles, `linkedin` to connect the authenticated user’s LinkedIn profile, or `youtube` to connect their YouTube channel.
+**platform:** `Whop_sdk::ExternalAccounts::Types::ConnectExternalAccountsRequestPlatform` — The platform to connect the external account on. Use `meta_business` to connect Meta Business assets, which is how Facebook Pages and Instagram accounts are connected — there is no separate `instagram` value. Use `tiktok` for TikTok accounts, `snapchat` for Snapchat Public Profiles, `linkedin` to connect the authenticated user’s LinkedIn profile, `youtube` to connect their YouTube channel, or `x` to connect their X profile.
     
 </dd>
 </dl>
@@ -19764,7 +19960,7 @@ client.external_accounts.connect(
 <dl>
 <dd>
 
-**scopes:** `Internal::Types::Array[Whop_sdk::ExternalAccounts::Types::ConnectExternalAccountsRequestScopesItem]` — The connection purpose. For `meta_business` and `snapchat`, `advertise` is required and connects company advertising assets. For `linkedin` and `youtube`, omit scopes to connect the authenticated user’s profile; advertising is not supported. For `tiktok`, omit scopes to connect the authenticated user’s profile, or pass `advertise` to connect company advertising assets. Profile connections still request the platform permissions needed to read the profile.
+**scopes:** `Internal::Types::Array[Whop_sdk::ExternalAccounts::Types::ConnectExternalAccountsRequestScopesItem]` — The connection purpose. For `meta_business` and `snapchat`, `advertise` is required and connects company advertising assets. For `linkedin`, `youtube`, and `x`, omit scopes to connect the authenticated user’s profile; advertising is not supported. For `tiktok`, omit scopes to connect the authenticated user’s profile, or pass `advertise` to connect company advertising assets. Profile connections still request the platform permissions needed to read the profile.
     
 </dd>
 </dl>
@@ -21941,6 +22137,9 @@ client.identity_profiles.retrieve_identity_profile(id: "idpf_xxxxxxxxxxxxx")
 <dd>
 
 Unlinks an identity profile from the account or user that owns `ledger_account_id`. Requires `identity:write` on that account or user.
+
+Required permissions:
+ - `identity:write`
 </dd>
 </dl>
 </dd>
@@ -26267,6 +26466,60 @@ client.partners.create
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.partners.<a href="/lib/whop_sdk/partners/client.rb">fee_options</a>() -> Whop_sdk::Partners::Types::FeeOptionsPartnersResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Lists, per income stream, the fee a business the caller refers would be charged, how low the caller may price it, and the commission the caller earns on that stream. Answers for a referral that does not exist yet, so a referral flow can price the deal before the business is created. Requires `partner:fees:update`, since the floors a partner may price down to are only for a credential that can set them.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.partners.fee_options
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::Partners::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>
@@ -26558,7 +26811,7 @@ client.partners.retrieve(id: "me")
 <dl>
 <dd>
 
-Lists the payment method domains registered for your account and its connected accounts.
+Lists the payment method domains registered for your account and its connected accounts. Deprecated: list domains with `GET /domains` and the `apple_pay` filter instead.
 </dd>
 </dl>
 </dd>
@@ -26708,7 +26961,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 `POST /payment_method_domains/:id/verify`.
+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`. Deprecated: add Apple Pay with `POST /domains` and `apple_pay: {}` instead.
 </dd>
 </dl>
 </dd>
@@ -26778,7 +27031,7 @@ client.payment_method_domains.create(hostname: "pending.shinetime.com")
 <dl>
 <dd>
 
-Retrieves a payment method domain to check its verification status.
+Retrieves a payment method domain to check its verification status. Deprecated: retrieve the domain with `GET /domains/{id}` instead, using the same ID.
 </dd>
 </dl>
 </dd>
@@ -26840,7 +27093,7 @@ client.payment_method_domains.retrieve(id: "id")
 <dl>
 <dd>
 
-Unregisters a payment method domain so its wallet payment methods stop rendering there.
+Unregisters a payment method domain so its wallet payment methods stop rendering there. Deprecated: remove Apple Pay with `PATCH /domains/{id}` and `apple_pay: null` instead. `DELETE /domains/{id}` removes the whole domain, including any website on it.
 </dd>
 </dl>
 </dd>
@@ -26902,7 +27155,7 @@ client.payment_method_domains.delete(id: "id")
 <dl>
 <dd>
 
-Re-attempts provider verification of a pending domain once the association file is hosted. Fails with a `bad_request` explaining what to fix; verifying an already `verified` domain is a no-op.
+Re-attempts provider verification of a pending domain once the association file is hosted. Fails with a `bad_request` explaining what to fix; verifying an already `verified` domain is a no-op. Deprecated: check the domain with `POST /domains/{id}/check` instead.
 </dd>
 </dl>
 </dd>
@@ -28952,6 +29205,14 @@ client.payments.refund(id: "id")
 <dl>
 <dd>
 
+**metadata:** `Internal::Types::Hash[String, String]` — Your own key-value data to attach to the refund, returned on it and on its `refund.created` and `refund.updated` webhooks. At most 50 keys; keys up to 100 characters and values up to 500.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **partial_amount:** `Integer` — The amount to refund, stated in this payment's `currency` like every other amount on it. When the buyer was billed in a different currency, it is converted at the payment's own exchange rate before the refund is issued. An amount that covers everything still refundable refunds the rest of the payment — omit it to refund the rest without having to work out what that is.
     
 </dd>
@@ -29971,7 +30232,7 @@ client.payouts.create_quote(
 <dl>
 <dd>
 
-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.
+Retrieves a payout by its `wdrl_` ID, or by the `cofr_` conversion request ID a 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>
@@ -30049,7 +30310,7 @@ client.payouts.retrieve(id: "id")
 <dl>
 <dd>
 
-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.
+Cancels a payout before it is sent to the payout provider, or asks the provider to stop one already sent. While the payout is `in_review`, or `processing` with nothing sent yet (see `cancelable`), it is canceled and the funds, fees included, return to the balance. Once sent, the response is 202 with a `cancellation` object, and the payout reads `canceled` only if the provider confirms it stopped. A `requested` payout returns 409 until it reaches review, a payout the provider can no longer stop returns 409 with error type `not_cancelable`, and canceling an already-canceled payout returns it unchanged.
 </dd>
 </dl>
 </dd>
@@ -35149,6 +35410,14 @@ client.setup_intents.create(account_id: "biz_xxxxxxxxxxxxxx")
 <dl>
 <dd>
 
+**owner_id:** `String` — Who the saved payment method belongs to. Pass `account_id` to save it on the account itself, which needs `payment:charge` on the account. Pass your own user ID, prefixed `user_`, to save it on the authenticated user. Omit it to save it on the buyer: the caller when it is the buyer, otherwise the user the confirmation token names. Not available with `payment_method_id`, which keeps its current owner, or with `purpose`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **payment_method_id:** `String` — An existing payment method to re-verify and save, prefixed `payt_`. Provide this or `confirmation_token`, not both. Not available to a buyer credential.
     
 </dd>
@@ -36023,7 +36292,7 @@ client.social_accounts.connect(
 <dl>
 <dd>
 
-**platform:** `Whop_sdk::SocialAccounts::Types::ConnectSocialAccountsRequestPlatform` — The platform to connect the external account on. Use `meta_business` to connect Meta Business assets, which is how Facebook Pages and Instagram accounts are connected — there is no separate `instagram` value. Use `tiktok` for TikTok accounts, `snapchat` for Snapchat Public Profiles, `linkedin` to connect the authenticated user’s LinkedIn profile, or `youtube` to connect their YouTube channel.
+**platform:** `Whop_sdk::SocialAccounts::Types::ConnectSocialAccountsRequestPlatform` — The platform to connect the external account on. Use `meta_business` to connect Meta Business assets, which is how Facebook Pages and Instagram accounts are connected — there is no separate `instagram` value. Use `tiktok` for TikTok accounts, `snapchat` for Snapchat Public Profiles, `linkedin` to connect the authenticated user’s LinkedIn profile, `youtube` to connect their YouTube channel, or `x` to connect their X profile.
     
 </dd>
 </dl>
@@ -36039,7 +36308,7 @@ client.social_accounts.connect(
 <dl>
 <dd>
 
-**scopes:** `Internal::Types::Array[Whop_sdk::SocialAccounts::Types::ConnectSocialAccountsRequestScopesItem]` — The connection purpose. For `meta_business` and `snapchat`, `advertise` is required and connects company advertising assets. For `linkedin` and `youtube`, omit scopes to connect the authenticated user’s profile; advertising is not supported. For `tiktok`, omit scopes to connect the authenticated user’s profile, or pass `advertise` to connect company advertising assets. Profile connections still request the platform permissions needed to read the profile.
+**scopes:** `Internal::Types::Array[Whop_sdk::SocialAccounts::Types::ConnectSocialAccountsRequestScopesItem]` — The connection purpose. For `meta_business` and `snapchat`, `advertise` is required and connects company advertising assets. For `linkedin`, `youtube`, and `x`, omit scopes to connect the authenticated user’s profile; advertising is not supported. For `tiktok`, omit scopes to connect the authenticated user’s profile, or pass `advertise` to connect company advertising assets. Profile connections still request the platform permissions needed to read the profile.
     
 </dd>
 </dl>
@@ -37025,6 +37294,14 @@ client.stats.retrieve(
 <dl>
 <dd>
 
+**product_category:** `String` — Filter to one product category, for example `algo_trading_course`. Pair with `breakdown_by=product_category` to split by product category. Available on metrics that list `product_category`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **issuer:** `String` — Filter to one card-issuing bank, named as the processor reports it, for example JPMORGAN CHASE BANK N A, or unknown for payments with no reported bank. Available on metrics that list issuer.
     
 </dd>
@@ -37415,6 +37692,14 @@ client.support_channels.list(
 <dl>
 <dd>
 
+**customer_user_ids:** `String` — Only return support channels opened by any of these customers. Maximum 100 IDs per request.
+    
+</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>
@@ -38037,7 +38322,7 @@ client.swaps.retrieve(id: "id")
 <dl>
 <dd>
 
-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.
+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. Members with the view-only Partner role are listed after all other members.
 </dd>
 </dl>
 </dd>
@@ -38099,6 +38384,38 @@ client.team_members.list(account_id: "account_id")
 <dl>
 <dd>
 
+**query:** `String` — Only return members whose name or username contains this text, and invites whose email contains it.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**reports_to_id:** `String` — Only return the direct reports of this team member, prefixed `ausr_`. Pass the account ID, prefixed `biz_`, for the members who report to the business directly. Pending invites are excluded, and the list pages in `created_at` order without moving Partner-role members last.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**direct_reports_min:** `Integer` — Only return members with at least this many direct reports. Pending invites are excluded, and the list pages in `created_at` order without moving Partner-role members last.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**direct_reports_max:** `Integer` — Only return members with at most this many direct reports; `0` returns the people who manage no one. Pending invites are excluded, and the list pages in `created_at` order without moving Partner-role members last.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **created_before:** `String` — Only return members added before this ISO 8601 timestamp.
     
 </dd>
@@ -38115,7 +38432,7 @@ client.team_members.list(account_id: "account_id")
 <dl>
 <dd>
 
-**order:** `Whop_sdk::TeamMembers::Types::ListTeamMembersRequestOrder` — Field used to sort members.
+**order:** `Whop_sdk::TeamMembers::Types::ListTeamMembersRequestOrder` — Field used to sort members. Members with the view-only Partner role are listed after all other members whichever way the list is sorted.
     
 </dd>
 </dl>
@@ -38454,101 +38771,6 @@ client.team_members.update(id: "id")
 </dl>
 
 
-</dd>
-</dl>
-</details>
-
-## Topups
-<details><summary><code>client.topups.<a href="/lib/whop_sdk/topups/client.rb">create</a>(request) -> Whop_sdk::Types::Topup</code></summary>
-<dl>
-<dd>
-
-#### 📝 Description
-
-<dl>
-<dd>
-
-<dl>
-<dd>
-
-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`
-</dd>
-</dl>
-</dd>
-</dl>
-
-#### 🔌 Usage
-
-<dl>
-<dd>
-
-<dl>
-<dd>
-
-```ruby
-client.topups.create(
-  account_id: "biz_xxxxxxxxxxxxxx",
-  amount: 6.9,
-  currency: "usd",
-  payment_method_id: "pmt_xxxxxxxxxxxxxx"
-)
-```
-</dd>
-</dl>
-</dd>
-</dl>
-
-#### ⚙️ Parameters
-
-<dl>
-<dd>
-
-<dl>
-<dd>
-
-**account_id:** `String` — The unique identifier of the company to add funds to, starting with 'biz_'.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**amount:** `Integer` — The amount to add to the balance in the specified currency. For example, 50.00 for $50.00 USD.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**currency:** `Whop_sdk::Types::Currencies` — The currency for the top-up amount, such as 'usd'.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**payment_method_id:** `String` — The unique identifier of the stored payment method to charge for the top-up.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**request_options:** `Whop_sdk::Topups::RequestOptions` 
-    
-</dd>
-</dl>
-</dd>
-</dl>
-
-
 </dd>
 </dl>
 </details>
@@ -38749,7 +38971,7 @@ client.trades.create(
 <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.
+**instrument_type:** `Whop_sdk::Trades::Types::CreateTradesRequestInstrumentType` — `perpetual` or `spot`. Required for an order. A spot order first switches the trading account to Hyperliquid's unified account mode, where spot and perpetuals share one USDC balance.
     
 </dd>
 </dl>
@@ -39066,7 +39288,7 @@ client.transfers.list
 <dl>
 <dd>
 
-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.
+Moves money between Whop balances or funds a claim link anyone with the URL can redeem. The `type` you send decides which object comes back.
 </dd>
 </dl>
 </dd>
@@ -41041,7 +41263,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 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.
+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` and `owners` add company formation documents and owners to the verification, and once everything is in this call sends the business for review — call it again after Update Verification to send it. Until then it stays `pending` and the hosted session collects anything left out. 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>
@@ -41181,7 +41403,7 @@ client.verifications.retrieve(id: "id")
 <dl>
 <dd>
 
-Updates editable profile details or submits answers for items returned in `requested_information`. Once a verification is `approved` its profile details are locked and can no longer be edited.
+Updates editable profile details or submits answers for items returned in `requested_information`. On a business verification still collecting details, company details, `documents`, and `owners` also go to the verification provider; call Create Verification again to send the business for review once everything is in. Under review, `registration_number`, `incorporation_date`, `place_of_incorporation`, and `documents` are refused. While the review waits on owners, owners can still be added, changed, or removed with `remove`; otherwise only an owner's missing documents can still be sent. Once a verification is `approved` its profile details are locked and can no longer be edited.
 </dd>
 </dl>
 </dd>
@@ -45416,7 +45638,7 @@ client.partners.businesses.list
 <dl>
 <dd>
 
-Retrieves a single referred business and its referral terms.
+Retrieves a single referred business and its referral terms. The original referrer or a caller with company:basic:read on the business credited for the referral can read it.
 </dd>
 </dl>
 </dd>
@@ -45478,7 +45700,7 @@ client.partners.businesses.retrieve(id: "id")
 <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.
+Save annual payment projections for a business referred by the authenticated partner. Unaccepted projections can be replaced with updated annual card and BNPL payment volume. To qualify, payment volume over the last 30 days must reach 5% of the annual payment projection. Ads are excluded from CPA; ordinary ad commissions continue. Pass withdraw_projections: true without projection amounts to remove unaccepted projections. Accepted projections are immutable. Public API access requires a partner OAuth token; business API keys are not supported.
 </dd>
 </dl>
 </dd>
@@ -45493,11 +45715,7 @@ Save annual projections for a business referred by the authenticated partner. Pr
 <dd>
 
 ```ruby
-client.partners.businesses.update(
-  id: "id",
-  annual_ads_usd: "120000",
-  annual_processing_usd: "1200000"
-)
+client.partners.businesses.update(id: "id")
 ```
 </dd>
 </dl>
@@ -45520,7 +45738,7 @@ client.partners.businesses.update(
 <dl>
 <dd>
 
-**annual_ads_usd:** `String` — Annual projected Whop Ads spend in USD.
+**annual_processing_usd:** `String` — Annual projected card and BNPL processing combined, in USD.
     
 </dd>
 </dl>
@@ -45528,7 +45746,7 @@ client.partners.businesses.update(
 <dl>
 <dd>
 
-**annual_processing_usd:** `String` — Annual projected processing on Whop in USD.
+**withdraw_projections:** `Internal::Types::Boolean` — Remove unaccepted projections and invalidate the offer. The original CPA term is retained if projections are later added again.
     
 </dd>
 </dl>
@@ -45578,7 +45796,7 @@ Accept the authenticated partner's CPA offer with the reviewed terms and signed
 client.partners.businesses.accept_commission_advance(
   id: "id",
   acknowledgments: %w[commission_replacement clawback term],
-  expected_amount_usd: "1439.99",
+  expected_amount_usd: "1079.99",
   offer_token: "eyJfcmFpbHMiOnsiZGF0YSI6MSwicHVyIjoiYmxvYl9pZCJ9fQ==--xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
   terms_version: "2026-01-01"
 )
@@ -45644,6 +45862,79 @@ client.partners.businesses.accept_commission_advance(
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.partners.businesses.<a href="/lib/whop_sdk/partners/businesses/client.rb">resend_invite</a>(id:, request) -> Whop_sdk::Partners::Businesses::Types::ResendInviteBusinessesResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Re-emails an outstanding invite to claim ownership of a referred business. Find the invite in the business's `pending_owner_invites`. Only the first-tier partner can resend, from a whop.com session or the Whop CLI or MCP with `partner:handoff`. Rate limited to one resend per invite every five minutes.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.partners.businesses.resend_invite(
+  id: "id",
+  invite_id: "ausri_xxxxxxxxxxxxxx"
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**id:** `String` — The partner business ID (a coma_ identifier).
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**invite_id:** `String` — The outstanding invite to resend (an ausri_ identifier from `pending_owner_invites`).
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::Partners::Businesses::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>
@@ -45661,7 +45952,7 @@ client.partners.businesses.accept_commission_advance(
 <dl>
 <dd>
 
-Lists the earnings Whop pays out for one referred business's activity, most recent first.
+Lists the earnings Whop pays out for one referred business's activity, most recent first. The original referrer or a caller with company:basic:read on the business credited for the referral can read them.
 </dd>
 </dl>
 </dd>
@@ -46804,7 +47095,7 @@ client.stats.reports.list
 <dl>
 <dd>
 
-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.
+Retrieves payments across all of Whop for up to four windows at once, optionally broken down by business type, industry type, product category, 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>
@@ -46906,6 +47197,14 @@ client.stats.reports.platform_trends
 <dl>
 <dd>
 
+**product_category:** `String` — Only counts payments for products in these comma-separated product categories, such as `algo_trading_course`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **account_country:** `String` — Only counts payments to accounts located in these comma-separated countries, as ISO 3166-1 alpha-2 codes such as `US`.
     
 </dd>
@@ -47350,6 +47649,14 @@ client.stats.time_series.retrieve(
 <dl>
 <dd>
 
+**product_category:** `String` — Filter to one product category, for example `algo_trading_course`. Pair with `breakdown_by=product_category` to split by product category. Available on metrics that list `product_category`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **issuer:** `String` — Filter to one card-issuing bank, named as the processor reports it, for example JPMORGAN CHASE BANK N A, or unknown for payments with no reported bank. Available on metrics that list issuer.
     
 </dd>
@@ -48383,6 +48690,69 @@ client.users.preferences.update
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+## Users Fees
+<details><summary><code>client.users.fees.<a href="/lib/whop_sdk/users/fees/client.rb">retrieve</a>(user_id:) -> Whop_sdk::Types::UserFees</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Retrieves the fees charged when the user moves money with their personal balance: withdrawals, transfers, bank deposits, and funding cards from pending balance. Each fee has the same shape as in Retrieve Account Fees. You can only retrieve your own fees, and they are read-only.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.users.fees.retrieve(user_id: "user_id")
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**user_id:** `String` — `me`, or the authenticated user's own `user_` tag or username.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Whop_sdk::Users::Fees::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>