Skip to main content
The Current API is versioned with dates. Breaking changes ship only inside a new dated version that you opt into. Pin a version and the request and response shapes you built against never change. Official SDKs automatically send the version used to generate them.
If you don’t pass an Api-Version-Date or have a stored API-key pin, the stable API model is used. Requests with neither are served by the pre-versioning behavior, so existing integrations keep working unchanged. Pin a dated version to opt into the latest API.

​
API key version pins

API keys carry their own API version pin. Requests authenticated with an API key use that pin when they omit Api-Version-Date. Existing keys without a stored pin use 2025-01-01. Newly created keys use the latest released version. An explicit Api-Version-Date header always takes precedence over the API key’s pin, so you can test an upgrade before changing the saved version. Every version automatically gets new endpoints and optional fields. Breaking changes create a new dated version, which the changelog below lists.

​
Changelog

​
Latest
Deposit destinations are an account ID
POST /deposits takes a destination account ID string — biz_… or user_… — and nothing else.
  • Raw wallet addresses are no longer accepted. Fund an account and read its addresses from methods.crypto.
  • The object form of destination ({ account_id } / { address, network }) is removed. Send the account ID on its own.
  • The top-level network override is removed. It never changed the response: every deposit already returns an address for every supported network, so pick the one you want from methods.crypto.
  • metadata is removed from both the request and the response. It was echoed back and never stored, so it couldn’t be used to reconcile a later deposit.
  • account_id on the response is no longer null, because every destination now names an account.
Pinned callers on an earlier version keep sending the object form and the removed inputs, and their responses still carry metadata — as an empty object rather than the value they sent. A wallet address is refused at every version: it never identified an account, so there is no older shape to keep serving.
​
Payments become a native resource
POST /payments, GET /payments and GET /payments/{id} are now served by the native Payments API, and the Payment object takes the shape of every other native resource.
  • Related records are foreign-key ids instead of embedded objects: account_id (was company), plan_id, product_id, membership_id, member_id, promo_code_id, shipment_id, payment_method_id. The buyer is a user summary (id, username, name, profile_picture).
  • Amounts are money objects ({ amount, currency, decimals, display_decimals }) instead of bare numbers: total, subtotal, tax_amount, refunded_amount, tax_refunded_amount, amount_after_fees, usd_total. settlement_amount, settlement_currency and settlement_exchange_rate are folded into total and currency. refunded_amount and tax_refunded_amount are stated as they settled, at the rate in force when each refund was issued, and tax_refunded_amount is now on list responses as well as retrieve.
  • Disputes, refunds and Resolution Center cases are no longer embedded — list them from their own endpoints with ?payment_id=. Embedded financing transactions and the application fee aren’t carried over to the native shape.
  • last_payment_attempt / next_payment_attempt are last_payment_attempt_at / next_payment_attempt_at. Card facts live on payment_instrument.
  • Creating a payment takes account_id (was company_id), answers 201 Created, honours Idempotency-Key, and accepts capture: false to place an authorization hold.
  • Native payment reads are account-scoped: the credential must be able to read the account’s payments (a team member’s token or the account’s API key). A buyer’s own user token, which the pinned proxy versions accept for reading their own payment, isn’t served natively yet — buyers keep working on their pinned version.
  • GET /payments/{id}/fees rows are { type, origin, label, description, amount, settlement_amount, collected_at } with money objects (were name/amount/currency/type).
  • GET /refunds and GET /refunds/{id} return the native Refund: payment_id and account_id instead of an embedded payment, amount as a money object in the payment’s settlement currency, original_amount in the processor’s currency. The company_id filter is account_id, and sending company_id is a 400.
  • POST /payments/{id}/refund, POST /payments/{id}/retry and POST /payments/{id}/void are native too, returning the same Payment object. Refund still takes an optional partial_amount.
  • GET /payments lists with the standard { data, page_info } envelope and cursor pagination. Filters are singular equality params (status, billing_reason, currency, plan_id, product_id, membership_id, member_id, user_id, account_id) instead of the proxy’s plural arrays. As on the proxy, billing_reason=subscription_cycle also matches renewals recorded as subscription_update. Zero-amount payments are included, so the proxy’s include_free is gone. An invalid status is a 400, as is any proxy-only filter (substatuses, updated_before/updated_after, checkout_configuration_ids, plural arrays), rather than an unfiltered page. The query buyer search works as before. The created_before/created_after window covers the payment’s creation time alone. The proxy filtered on paid-at where one existed. On list rows settlement_time_at is null — retrieve the payment for it.
​
Legacy ad reports endpoint retired
The legacy GET /ad_reports endpoint is deprecated in favor of the native Stats metrics and the ad entity endpoints. It’s no longer served at this version.
  • GET /ad_reports returns 410 Gone with an error.type of gone. Use GET /stats/ad_delivery for spend, impressions, and clicks over time, scoped with a source path such as whop:adcamp_xxx:*. Use GET /stats/events for attributed conversions.
  • Per-entity performance for a window is on the entity endpoints. GET /ad_campaigns, GET /ad_groups, and GET /ads accept stats_from and stats_to and return spend, results, and return_on_ad_spend on each row.
  • Every response from the legacy endpoint, at any version, now carries Deprecation and Link: <…/stats/ad_delivery>; rel="successor-version" headers. Requests pinned to earlier versions, and requests without a version, keep working unchanged until a Sunset header announces the date it stops responding for every version.
​
Financial report timestamp ranges
GET /financial_reports and GET /financial_reports/breakdown now use from and to ISO 8601 timestamps for report windows.
  • from_date and to_date are renamed to from and to.
  • Bare dates are no longer accepted. Include a time and offset in both timestamps.
​
Explicit app verification filtering
GET /apps now uses verified as an optional equality filter instead of treating its absence as verified=false for public website lists.
  • Omit verified to return publicly discoverable website blueprints from both verification states.
  • Set verified=true for Whop-verified blueprints or verified=false for community blueprints.
  • recommended=true filters recommended apps independently of verification status.
​
Legacy withdrawals endpoints retired
The legacy /withdrawals endpoints are deprecated in favour of the native Payouts API and are no longer served at this version.
  • GET /withdrawals and POST /withdrawals return 410 Gone with an error.type of gone. Use GET /payouts and POST /payouts instead. Payout ids are the same wdrl_ ids, so existing identifiers keep resolving.
  • GET /withdrawals/{id} still responds at this version. Use GET /payouts/{id} for new work.
  • Every response from the legacy endpoints, at any version, now carries Deprecation and Link: <…/payouts>; rel="successor-version" headers. A Sunset header will announce the date they stop responding for every version. Until then, requests pinned to earlier versions, and requests without a version, keep working unchanged.
​
Ad post IDs
An ad’s post_id now names the post the ad network serves, whichever way the ad was built.
  • post_id returns the network’s post for the ad — the one Meta created for an uploaded creative, or the post being promoted. It used to be null for every ad built from uploaded creatives.
  • The post you point an ad at moved to existing_post_id, on both the response and the create/update body. post_source and post_thumbnail_url describe that field.
​
Native Files API
POST /files and GET /files/{id} are served natively with a redesigned file object, and multipart uploads finish through the new POST /files/{id}/complete.
  • File responses carry the standard envelope: object, visibility, and an ISO 8601 created_at. The size and url fields are null until the upload is ready.
  • GET /files/{id} only resolves files you created — other callers receive a 404.
​
Payouts status v2
The payout object’s lifecycle vocabulary is rebuilt and its money fields become decimal strings.
  • status speaks eight words: requested, in_review, processing, completed, reversed, canceled, failed, denied. A settled payout the provider reverses reads reversed, with the return code and funds_returned_at in failure.
  • A new status_detail field carries the finest machine phase under the status word. Its values can grow without a version bump — status is the versioned contract.
  • amount, fee_amount, net_amount, markup_fee, and destination_amount are decimal strings. exchange_rate stays a number.
  • Payouts are created under their wdrl_ id: the id POST /payouts returns is the id GET /payouts lists, and a stablecoin payout’s conversion request survives as payout_request_id. Conversion requests created before this version keep answering under their cofr_ id.
  • The idempotency key is sent only in the Idempotency-Key header, and the idempotency_key body field is rejected.
Requests pinned to earlier versions keep the previous vocabulary, float money, and body-field idempotency keys. Webhook payloads follow the subscription’s api_version_date the same way: subscriptions pinned 2026-08-21 or later receive the new payout shape, earlier or unpinned subscriptions keep the previous one.
​
Webhook envelope account_id
The webhook envelope’s company_id field is renamed to account_id.
  • Webhook deliveries pinned to 2026-08-14 or later carry account_id in the envelope.
  • Webhooks pinned to earlier versions — and webhooks without an api_version_date pin — keep company_id.
​
In-transit balance breakdowns
Account and personal balance breakdowns now expose in_transit alongside pending.
  • Add pending and in_transit to present the total amount awaiting settlement.
  • Callers pinned to earlier versions continue receiving the combined amount in pending.
​
Webhook API version input removed
The api_version input on POST /webhooks and PATCH /webhooks/{id} is removed.
  • New webhooks always use the v1 events and payloads. Requests passing api_version are rejected with a 400.
  • Pin a webhook’s payload shape with api_version_date instead.
  • Existing v2 and v5 webhooks keep delivering. You can no longer create or switch webhooks to these versions.
​
Native dispute alert endpoints
Dispute alerts are now a native REST resource and remain dual-served with the legacy proxy.
  • GET /dispute_alerts lists an account’s alerts with cursor pagination, and filters by account_id, payment_id, type, and a creation window.
  • type replaces alert_type and names the two kinds an issuer sends: early_fraud_warning (Visa TC40 / Mastercard SAFE fraud reports) and dispute_alert (pre-dispute notices).
  • fee_charged replaces charge_for_alert and reports whether Whop actually billed the account. Early fraud warnings are never billed.
  • actionable reports whether refunding the payment can still prevent a chargeback.
  • payment and dispute objects are replaced by the payment_id and account_id tags. Timestamps are ISO 8601, with reported_at for when the issuer filed the report.
​
Fiat currency conversion on swaps
Fiat-pair swaps (POST /swaps with two fiat currencies) now support free-form currency conversion, and amount matches crypto swap semantics.
  • amount is the amount of from_token to convert at the mid-market rate. No negative balance is required.
  • Sizing a partial repayment of a negative to_token balance moved to the new to_amount field (denominated in to_token, capped at the debt). amount and to_amount are mutually exclusive.
  • Omitting both still repays the full negative to_token balance.
  • Callers pinned to earlier versions keep the previous behavior: their fiat amount is treated as the to_token repayment amount.
​
Flat verification requirements
A verification’s requested_information is now a flat list: one requirement per entry, one write per answer.
  • Each entry names what’s needed in requirement: a document such as bank_statement, or a field key such as ssn, with a label to show the user.
  • Answer file entries with file (a direct upload ID). Answer text, date, phone, and select entries with value, and address entries with address. Nothing from the response is echoed back.
  • An entry marked multiple takes several files in one answer, in slot order, front first for a two-sided document.
  • An entry listing options also takes a value. For select entries, the options are the allowed answers. For identity documents, the options are the accepted ID types.
  • Keys that don’t apply are omitted, and rejected submissions carry structured errors with a stable code and a reason.
  • The nested requested_files/category form shape is gone from this version. Callers pinned to earlier versions keep it, and their answers are translated automatically.
​
Native promo code endpoints
Promo codes are now a complete top-level REST resource and remain dual-served with the legacy proxy.
  • GET /promo_codes lists an account’s promo codes and uses account_id instead of company_id.
  • POST /promo_codes creates promo codes. GET and DELETE /promo_codes/{id} retrieve and archive them.
  • POST /promo_codes/{id}/activate and POST /promo_codes/{id}/deactivate replace the legacy PATCH status write.
  • List responses use cursor pagination and support status, product, plan, timestamp, and sorting filters.
  • Callers pinned to earlier versions keep the legacy proxy contract unchanged.
​
Richer parent accounts
Account responses now expose a richer parent account relationship for connected accounts.
  • parent_account replaces parent_account_id.
  • The parent account includes its id, title, route, and logo_url.
​
Supported payout methods
Supported payout methods now have their own paginated endpoint.
  • GET /payouts/supported_methods lists the payout methods an account or user is eligible to add.
  • Supported methods use object: "supported_payout_method", and their podst_ IDs are passed as supported_payout_method_id.
  • Saved payout methods expose supported_payout_method. Payouts expose payout_method.supported_payout_method.
  • Use country to list supported methods for a country other than the payout account’s country.
  • GET /payouts/methods no longer accepts include_available or returns available_destinations.
  • Callers pinned to earlier versions keep destination_id, payout_destination, and payout_token.
​
Native card transactions, payout method arrival estimates
Card transactions now use native REST endpoints and remain dual-served with the legacy proxy.
  • GET /card_transactions lists an account’s card transactions, and GET /card_transactions/{id} retrieves one by its citx_ id. The list also takes a transaction_ids filter to fetch specific transactions in one request.
  • Card transactions are account-scoped: the owner is selected with account_id, defaulting to the account the credential belongs to.
  • Filters on transaction_ids, card_id, cardholder_id, status, created_after, and created_before. Timestamp filters are ISO 8601.
  • cardholder_id is new on the response: the user the card is assigned to.
Payout methods now carry amount-independent fee and delivery terms, and the quote no longer duplicates arrival estimates.
  • Each payout method returns fee_structure (percentage, fixed amount, and currency) and estimated_arrival (per-speed timestamps) without requiring an amount.
  • The quote’s standard and instant objects no longer include estimated_arrival. Read it from the method’s top-level estimated_arrival field.
​
Native Resolution Center endpoints
Resolution Center cases now use native REST endpoints and remain dual-served with the legacy proxy.
  • status, escalated, outcome, refund, reason, and available_actions expose case state and permitted actions.
  • Events are available from paginated GET /resolution_center_cases/{id}/events. Summaries are available from GET /resolution_center_cases/summary.
  • Writes use message and attachments. due_date is renamed response_due_at. Listing no longer requires account_id.
​
Native shipments endpoints
Shipments now use native REST endpoints and remain dual-served with the legacy proxy.
  • GET /shipments lists shipments. GET /shipments/{id} retrieves by shipment id or payment id.
  • POST /shipments creates a shipment, and PATCH /shipments/{id} updates its tracking number.
  • Responses use account_id and tracking_number, alongside carrier, tracking_url, order_id, and payment_id.
  • Callers pinned before this date keep the legacy proxy contract unchanged.
​
Native disputes endpoints
Disputes now use native REST endpoints and remain dual-served with the legacy proxy.
  • PATCH /disputes/{id} edits evidence, and POST /disputes/{id}/submit submits it. Evidence is nested under evidence.
  • GET /disputes/summary provides totals grouped by status and currency. List and retrieve return the same fields.
  • Responses use account_id, product_id, and plan_id, plus buyer alongside payment. Listing no longer requires account_id.
  • status and reason are normalized enums, and needs_response_by, rdr, and editable are replaced by their new fields.
  • Callers pinned before this date keep the legacy proxy contract unchanged.
​
Members and memberships
Members and memberships now use native resources with an account-oriented membership model and redesigned lifecycle actions.
  • Membership responses return plan_id and product_id instead of nested plan and product objects.
  • Listing memberships returns everything the caller can read (their own plus their managed accounts’) and account_id/user_id narrow that list instead of switching modes or erroring.
  • Set cancel_at_period_end to schedule cancellation. The cancel action ends access immediately.
  • The extend action replaces add_free_days.
​
REST response and timestamp consistency
The Current API now uses consistent delete responses, timestamp inputs, and Account naming.
  • Delete endpoints for products, plans, checkout configurations, ads, ad groups, ad campaigns, social accounts, and bounty submissions return { id, deleted: true } instead of a bare boolean.
  • Timestamp filters on products, plans, checkout configurations, transfers, and financial reports accept ISO 8601 only instead of also accepting epoch seconds.
  • Product responses return account instead of company.
​
Partner business payout percentages
Partner businesses now expose separate payout rates for every income source.
  • payout_percentage is replaced by payout_percentages.
  • The nested object includes sales, ad_spend, transfer, and card_interchange rates.
​
Products and checkout configurations
Products and checkout configurations now use the Account model consistently.
  • Product request parameters use account_id instead of company_id.
  • Checkout configuration requests use account_id at the top level and inside inline plan objects.
  • Checkout configuration responses return account_id instead of company_id.
​
Checkout configuration timestamps
Checkout configuration timestamps now use the same format as the rest of the API.
  • created_at and updated_at are ISO 8601 strings instead of Unix epoch integers.
​
User balances
User balances now provide a complete, structured balance summary.
  • The flat total_usd and balances fields are replaced by a nested balance object.
  • The summary separates cash, crypto, in-flight treasury deposits, and balances for accounts the user owns.
​
Business referral earnings resources
Business referral earnings now identify the polymorphic resource that generated the earning.
  • receipt is replaced by resource.
  • access_pass is replaced by product.
  • Receipt-backed earnings return resource.object: "receipt" with receipt payment details.
  • The resource field can support additional earning resources in future versions without reusing receipt-specific fields.
​
Business referrals resource
Business referral volume and earnings are now reported as reconciling groups.
  • processing_volume, total_earnings, pending_payout, and completed_payout are replaced by nested volume_usd and earnings_usd objects.
  • Earnings rename base_amount/amount to transaction_amount_usd/commission_amount_usd and express payout_percentage as a fraction.
​
Plans resource
Plans now use the Account model consistently.
  • Request parameters and request bodies use account_id instead of company_id.
  • Plan responses return account instead of company.
​
Users resource
User access requests now use the Account model consistently.
  • Request parameters and request bodies use account_id instead of company_id.
  • Response shapes are unchanged.
​
Original version
The original Current API behavior before dated versioning existed.Requests without Api-Version-Date use this version so existing integrations keep working.