> ## Documentation Index > Fetch the complete documentation index at: https://docs.whop.com/llms.txt > Use this file to discover all available pages before exploring further. # Submit Dispute > Sends the dispute's evidence packet to the payment processor and moves the dispute to `under_review`. This is final — the packet cannot be edited or resent afterwards. ## OpenAPI ````yaml /openapi/api-v1-native.json post /disputes/{id}/submit openapi: 3.1.0 info: description: >- The Whop REST API. Please see https://docs.whop.com/developer/api/getting-started for more details. termsOfService: https://whop.com/tos-developer-api/ title: Whop API version: 1.0.0 x-api-version-date: '2026-07-25' servers: - description: Production Whop API url: https://api.whop.com/api/v1 - description: Sandbox Whop API url: https://sandbox-api.whop.com/api/v1 security: [] tags: - description: > An Account represents a person or business on Whop that can have its own profile, wallet, and account-scoped settings. Use accounts for customers, creators, merchants, sellers, or connected businesses your integration supports. Use the Accounts API to create accounts, list accounts visible to your credentials, retrieve or update an account, and retrieve the account associated with the current API key. name: Accounts x-whop-summary: 'A business on Whop: profile, wallet, capabilities, settings.' - description: > A User represents a person on Whop. Users have a public profile and can buy products, join accounts, and access experiences. Use the Users API to search for users, retrieve or update profiles, and check whether a user has access to an account, product, or experience. name: Users x-whop-summary: 'A person on Whop: profile and connected identities.' - description: > A Team Member is a member of an account's team: the link between a user and an account, carrying the role that controls what they can do. Roles are either system roles (like `admin` or `moderator`) or `custom` roles managed from the dashboard. Use the Team Members API to list an account's team, add a user to the team with a system role, change a member's role, and remove members. Adding a user who has not yet accepted sends an invitation instead. name: Team Members x-whop-summary: An account's team members and the roles that scope their access. - description: > A Member is one buyer's relationship with an account — one record per customer regardless of how many memberships they hold. It carries relationship-level state: whether they have joined or left, their access level (`customer`, `admin`, or `no_access`), when they joined, and when they last opened the account's content. Use the Members API to list an account's members with filtering by access level, status, join date, and name or username search, and to retrieve a single member. Member rows are created and maintained by the membership lifecycle; to grant or revoke access, work with memberships instead. name: Members x-whop-summary: One buyer's relationship with an account, across all their purchases. - name: Webhooks x-whop-summary: Event notifications pushed to your server as things happen. - description: > Stats represent aggregated activity for an account over time. They help you understand revenue, transactions, disputes, members, referrals, and advertising performance across reporting periods like days, weeks, or months. Use the Stats API to list available metrics and their filterable properties, then retrieve time-series values for a date range. name: Stats x-whop-summary: Aggregated financial, audience, and traffic reporting. - description: > A Verification represents a legal identity for a person or business. Accounts and users complete verification when Whop needs to confirm who they are before enabling payouts or compliance-sensitive workflows. Use the Verifications API to start or resume a hosted verification session, check review status, and submit requested details or documents. If `requested_information` contains items, submit answers with [Update Verification](/api-reference/beta/verifications/update-verification). name: Verifications x-whop-summary: Legal identity required before payouts and card issuing. - description: > A Ledger Activity row is a single financial event on an account's ledger — a payment, withdrawal, refund, transfer, on-chain deposit, swap, or card transaction. Each row is derived from the underlying ledger lines and carries a typed `resource` and `source` so you can present and link the event without extra lookups. Use Ledger Activity to build a statement or transaction feed for an account or user. Reconcile against your own records with `amount` (signed, in the currency's smallest precision units) and `posted_at`, and use `available_at` to know when inflows became withdrawable. name: Ledgers x-whop-summary: The activity feed behind an account or user's balance. - description: > Payouts represent money sent from an account or user balance to an external destination, such as a bank account, wallet, or other saved payout method. Use the Payouts API to create payouts from stablecoin accounts, list payout history for accounts or users, monitor payout statuses, and show expected arrival details for funds leaving Whop. name: Payouts x-whop-summary: Send money from a balance to a bank or wallet. - description: > Cards represent Whop-issued virtual payment cards that spend from an account or user balance. Cards can be assigned to cardholders and configured with spending limits for controlled spending. Use the Cards API to issue cards, list cards for an account or user, and retrieve active card details such as the card number and CVC. name: Cards x-whop-summary: Issue cards that spend from a balance. - description: > Transfers move value between identities on Whop. They are used for account-to-account money movement, user payouts inside Whop, crypto transfers, and claim links depending on the destination type. Use the Transfers API to create a transfer, list previous transfers, and retrieve a transfer by ID when reconciling money movement between accounts or users. name: Transfers x-whop-summary: Move funds between Whop accounts and users. - description: > A Dispute is a chargeback a customer files against a payment through their bank, or a pre-dispute inquiry that may become one. It carries the disputed payment, a deadline to respond, the evidence packet you send to the payment processor, and the outcome once the processor rules. Disputes are opened by the customer's bank, never through the API, so you can read them but not create or delete them. Use the Disputes API to list and filter disputes, summarize them by status and currency for a queue view, edit the evidence packet while the dispute is still contestable, and submit that evidence for review. name: Disputes x-whop-summary: Chargebacks filed against an account, with evidence and outcomes. - description: > Deposits describe ways to add funds to an account balance, including hosted deposit pages, bank deposit instructions, and supported crypto wallet addresses. Use the Deposits API to create deposit instructions for an account. name: Deposits x-whop-summary: Add funds to a balance. - description: > Swaps convert value between supported tokens, chains, or wallet destinations for an account. A swap quote describes the expected output, fees, and approval requirements before you create the swap. Use the Swaps API to quote a conversion, create the swap, list recent swaps, and retrieve status until the transaction completes. name: Swaps x-whop-summary: Convert a balance between currencies. - description: > A Product is a digital good or service sold on Whop. Products may contain plans for pricing and/or experiences for content delivery. Use the Products API to create products, list products visible to your credentials, retrieve product details, update product metadata or merchandising fields, and delete products that should no longer be sold. name: Products x-whop-summary: The things you sell. Each owns plans and a store page. - description: > A Plan defines how customers buy a product. It controls pricing, billing cadence, availability, tax behavior, checkout fields, and purchase visibility. Use the Plans API to create plans for products, list existing plans, retrieve or update plan configuration, calculate tax for checkout, and delete plans that should no longer be offered. name: Plans x-whop-summary: 'Pricing for a product: one-time, recurring, trials, stock.' - description: > A Membership is a customer's purchase of a plan: the subscription or one-time grant that gives them access to a product. It tracks billing state (`active`, `trialing`, `past_due`, and so on), the current period, pending cancellations, custom metadata, and the software license key when the product includes licensing. Use the Memberships API to list an account's memberships or the caller's own, retrieve one by ID or license key, and manage the lifecycle: cancel immediately or at period end, reverse a scheduled period-end cancellation, pause and resume payment collection, extend with free days, and update metadata. name: Memberships x-whop-summary: A customer's purchase of a plan, from checkout through cancellation. - description: > A Checkout Configuration is a reusable checkout link owned by an account. In `payment` mode it sells a specific plan; in `setup` mode it collects and saves payment details without charging. Each configuration can also override which payment methods are accepted and how 3D Secure is enforced for that checkout. Use the Checkout Configurations API to create checkout links for an existing or inline plan, list configurations for an account, retrieve the configuration behind a checkout URL, and delete links that should no longer be used. name: Checkout Configurations x-whop-summary: Turn a plan into a shareable, prefilled checkout link. - description: > The Partners API covers your Whop partner activity: the users you referred onto Whop, the businesses you referred and the earnings generated from their processing volume, and the partner leaderboard. Use it to enroll as a Whop partner, list the users you referred, list your referred businesses and review their earnings, and see the partner leaderboard. name: Partners x-whop-summary: >- The users and businesses you referred to Whop, and what you earn from them. - description: > A Bounty is a paid task posted by an account or user. The reward is held in escrow when the bounty publishes, workers submit proof of completed work, and each accepted submission is paid out until every winner slot fills. Use the Bounties API to create and publish a bounty, list an account's bounties for reporting or dashboards, list the bounties a user can work or has participated in, and retrieve a single bounty by ID. name: Bounties x-whop-summary: Paid tasks with reviewed submissions and escrowed rewards. - description: > A Bounty Submission is one worker's attempt on a bounty. It starts as an in-progress attempt, enters the review queue when proof is submitted, and ends approved (paid from the bounty's escrowed pool) or denied. Use the Bounty Submissions API to submit proof of completed work to a bounty, list the submissions you authored, and review the submissions on your bounties — across every bounty or narrowed to one. name: Bounty Submissions x-whop-summary: Work submitted to a bounty, from attempt to payout. - description: > A Person is an identity-linked profile of a visitor or customer of an account, assembled from every [event](/api-reference/beta/events/event) the person generated — pixel page views, ad clicks, leads, identifies, and payments. Each profile carries the person's known identities (names, emails, phones, user IDs), purchase history and LTV, geo/device profile, traffic sources, and the first and last marketing touches that reached them. Use the People API to list and segment the people of an account — filter by activity, purchases, traffic source, location, or marketing touch, and sort by value — or retrieve one person by person ID, user ID, email address, or phone number. name: People x-whop-summary: >- Visitors and customers of an account, with identity, purchase, and traffic profiles. - description: > An Event records conversion or engagement activity for an account, such as page views, purchases, or leads. Each event ties the action to the [person](/api-reference/beta/people/person) who took it, so activity can be attributed to the ads and links that drove it. Use the Events API to send new tracking events, list recent identity-linked events for an account, and inspect the events recorded for a person. name: Events x-whop-summary: Conversion and engagement events tracked for attribution. - description: > An Ad is the individual creative unit delivered by an [ad group](/api-reference/beta/ad-groups/ad-group). It holds the copy, creative assets, and destination URL for one ad. Use the Ads API to list ads for an account, create ads inside ad groups, retrieve or update creative details, delete ads that should stop running, and pause or resume delivery. name: Ads x-whop-summary: 'The creative: copy, assets, and destination URL.' - description: > An Ad Campaign is the top-level container for paid ads on an ad network. It sets the platform, objective, and budget strategy shared by its [ad groups](/api-reference/beta/ad-groups/ad-group) and ads. Use the Ad Campaigns API to create campaigns, list campaigns for an account, retrieve or update campaign settings, and pause or resume campaign delivery. name: Ad Campaigns x-whop-summary: Platform, objective, and budget for a set of ads. - description: > An Ad Group sits inside an [ad campaign](/api-reference/beta/ad-campaigns/ad-campaign) and controls delivery for [ads](/api-reference/beta/ads/ad). It sets the audience, placements, schedule, budget, and optimization goal for its ads. Use the Ad Groups API to create ad groups in campaigns, list or retrieve targeting and delivery settings, update budgets or targeting, delete groups that should stop running, and pause or resume delivery. It can also search the ad platform's targeting taxonomy for options to target and estimate how many people a draft targeting spec can reach. name: Ad Groups x-whop-summary: Audience, placements, and schedule within a campaign. - description: > An Audience represents a customer list uploaded to Whop for ad targeting. Audiences belong to an account and sync to supported ad platforms as custom audiences. Use the Audiences API to create audiences from CSV uploads, monitor processing status, and list or delete audiences for an account. Created audiences are usable for targeting after processing reaches `ready` or `partial`. name: Audiences x-whop-summary: Reusable targeting lists for ad groups. - description: > A Media Asset is an AI-generated image or video created from a prompt and billed from an account balance. When generation finishes, the asset includes a file that can be attached anywhere Whop accepts files. Use the Media API to start a generation job and retrieve the asset while it processes or after it is ready. name: Media x-whop-summary: >- AI-generated assets, billed from a balance, attachable wherever files are accepted. - description: > A Social Account represents an external profile connected to a Whop account or user, such as a Facebook page or Instagram account. Connecting a social account lets Whop run [ads](/api-reference/beta/ads/ad) under that profile's identity and promote its existing posts. Use the Social Accounts API to list connected accounts, create a Whop-managed Facebook page, start an OAuth connection, disconnect a social account, and list a connected profile's posts or a Facebook page's lead forms. name: Social Accounts x-whop-summary: Connected Facebook and Instagram accounts that run ads. - description: > An App is software you build on Whop. It can be a hosted web app served at `.whop.app` or an API integration installed as an experience, and it belongs to the account that owns its credentials, settings, builds, and runtime logs. Use the Apps API to manage app configuration and, for hosted apps, read server runtime logs for console output, uncaught exceptions, and failed requests. Logs are retained for 7 days and can be filtered by build, level, time window, and message text. name: Apps x-whop-summary: 'Apps you build on Whop: metadata, hosted builds, runtime logs.' - description: > An App Build is a versioned artifact uploaded for an app — a hosted web archive, or an iOS/Android bundle. Builds start as drafts, go through review, and one approved build per platform is served to users as the production build. Use the App Builds API to upload a build for an app, list an app's builds with platform and status filters, retrieve a build, and promote a draft or approved build to production. name: App Builds x-whop-summary: Versioned build artifacts deployed to an app's platforms. - description: > An API Key is a programmatic credential owned by an account or app. Each key carries its own permissions policy — explicit permission statements or an inherited system role — and can be restricted with an expiration date and an IP allowlist. Use the API Keys API to list a company or app's keys, create a key (the full secret is returned once, on creation), inspect a key's effective grants, update its name or restrictions, rotate its secret, and revoke it. These endpoints require a user session — they cannot be called with an API key. name: API Keys x-whop-summary: Programmatic credentials for an account or app. paths: /disputes/{id}/submit: parameters: - description: The dispute ID (`dspt_` tag). in: path name: id required: true schema: type: string post: tags: - Disputes summary: Submit Dispute description: >- Sends the dispute's evidence packet to the payment processor and moves the dispute to `under_review`. This is final — the packet cannot be edited or resent afterwards. operationId: submitDispute parameters: - $ref: '#/components/parameters/ApiVersionDate' - $ref: '#/components/parameters/IdempotencyKey' responses: '200': content: application/json: schema: $ref: '#/components/schemas/Dispute' description: dispute submitted '400': $ref: '#/components/responses/InvalidParameters' description: the dispute's evidence can no longer be submitted '401': $ref: '#/components/responses/Unauthorized' description: missing or invalid authentication '404': $ref: '#/components/responses/NotFound' description: no dispute with that ID security: - bearerAuth: - payment:dispute x-codeSamples: - lang: JavaScript source: |- import Whop from '@whop/sdk'; const client = new Whop({ apiKey: process.env['WHOP_API_KEY'], // This is the default and can be omitted }); const dispute = await client.disputes.submit('id'); console.log(dispute.id); components: parameters: ApiVersionDate: description: Pins the request to a dated API version. in: header name: Api-Version-Date required: false schema: example: '2026-07-25' type: string IdempotencyKey: description: >- A unique key that makes this request safe to retry. See [Idempotent requests](https://docs.whop.com/developer/api/idempotency). in: header name: Idempotency-Key required: false schema: example: d9105228-4a08-46b1-8b91-42fed586d383 maxLength: 255 type: string schemas: Dispute: properties: account_id: description: The account the dispute was filed against, prefixed `biz_`. type: - string - 'null' amount: description: The disputed amount, in whole units of `currency`. type: number buyer: description: The customer who filed the dispute. oneOf: - $ref: '#/components/schemas/DisputeBuyer' - type: 'null' created_at: description: When the dispute was opened, as an ISO 8601 timestamp. type: string currency: description: Three-letter ISO currency code of the disputed amount. type: string evidence: $ref: '#/components/schemas/DisputeEvidence' description: The evidence packet sent to the processor to contest the dispute. evidence_due_at: description: >- The deadline to submit evidence, as an ISO 8601 timestamp. Whop reserves the last 24 hours before the processor's own cutoff to forward the submission. type: - string - 'null' evidence_editable: description: Whether `evidence` can still be changed and submitted. type: boolean evidence_locked_reason: description: >- Why evidence can no longer be edited. `null` while `evidence_editable` is true. enum: - submitted - response_window_closed - not_contestable - null example: submitted type: - string - 'null' evidence_submitted_at: description: >- When the evidence was submitted to the processor, as an ISO 8601 timestamp. type: - string - 'null' id: description: Dispute ID, prefixed `dspt_`. type: string inquiry: description: >- Whether this is a pre-dispute inquiry rather than a formal chargeback. Inquiries follow the same lifecycle but move no funds unless one escalates. type: boolean payment: description: The payment being disputed. oneOf: - $ref: '#/components/schemas/DisputePayment' - type: 'null' plan_id: description: The plan the disputed payment was made on, prefixed `plan_`. type: - string - 'null' product_id: description: The product the disputed payment was for, prefixed `prod_`. type: - string - 'null' rapid_dispute_resolution: description: >- Whether Visa Rapid Dispute Resolution settled this automatically. These refund the customer without an evidence round. type: boolean reason: description: >- Why the customer says they are disputing, normalized across card networks. `other` covers a code Whop has not categorized yet — read `reason_code` for the raw value. enum: - fraudulent - unrecognized - declined_authorization - product_not_received - product_unacceptable - subscription_canceled - credit_not_processed - duplicate - processing_error - documentation_request - bank_cannot_process - other example: fraudulent type: string reason_code: description: The raw card-network or processor reason code, such as `10.4`. type: - string - 'null' status: description: >- Where the dispute stands. `needs_response` is awaiting evidence, `under_review` is with the processor, `won` returned the funds to the seller, `lost` returned them to the customer, and `closed` ended without a ruling. enum: - needs_response - under_review - won - lost - closed example: needs_response type: string updated_at: description: When the dispute was last changed, as an ISO 8601 timestamp. type: string required: - id - status - inquiry - amount - currency - reason - reason_code - account_id - product_id - plan_id - rapid_dispute_resolution - evidence_editable - evidence_locked_reason - evidence_due_at - evidence_submitted_at - buyer - payment - evidence - created_at - updated_at type: object DisputeBuyer: properties: email: description: >- The customer's email address. Requires the `member:email:read` scope; `null` without it. type: - string - 'null' member_id: description: The customer's member row on the account, prefixed `mem_`. type: - string - 'null' name: description: The customer's display name. type: - string - 'null' user_id: description: >- The customer's user ID, prefixed `user_`. `null` for a guest checkout. type: - string - 'null' username: description: The customer's Whop username. type: - string - 'null' required: - user_id - member_id - name - username - email type: object DisputeEvidence: properties: access_activity_log: description: >- Log of the customer's access to the product, such as sign-in or download activity. type: - string - 'null' billing_address: description: The billing address the customer provided at checkout. type: - string - 'null' cancellation_policy_attachment: description: >- The cancellation policy document. Falls back to Whop's platform policy when the seller has not uploaded their own. oneOf: - $ref: '#/components/schemas/DisputeAttachment' - type: 'null' cancellation_policy_disclosure: description: >- How the cancellation policy was shown to the customer before purchase. type: - string - 'null' customer_communication_attachment: description: Correspondence with the customer, or proof they used the product. oneOf: - $ref: '#/components/schemas/DisputeAttachment' - type: 'null' customer_email_address: description: The email address the customer used at checkout. type: - string - 'null' customer_name: description: The customer's name as given at checkout. type: - string - 'null' notes: description: Any additional context for the processor reviewing the dispute. type: - string - 'null' product_description: description: What the customer purchased, in the seller's own words. type: - string - 'null' refund_policy_attachment: description: >- The refund policy document. Falls back to Whop's platform policy when the seller has not uploaded their own. oneOf: - $ref: '#/components/schemas/DisputeAttachment' - type: 'null' refund_policy_disclosure: description: How the refund policy was shown to the customer before purchase. type: - string - 'null' refund_refusal_explanation: description: Why a refund was refused, when one was requested and denied. type: - string - 'null' service_date: description: When the product or service was delivered. type: - string - 'null' uncategorized_attachment: description: Supporting evidence that does not fit the other categories. oneOf: - $ref: '#/components/schemas/DisputeAttachment' - type: 'null' required: - access_activity_log - billing_address - cancellation_policy_disclosure - customer_email_address - customer_name - notes - product_description - refund_policy_disclosure - refund_refusal_explanation - service_date - cancellation_policy_attachment - customer_communication_attachment - refund_policy_attachment - uncategorized_attachment type: object DisputePayment: properties: amount: description: >- What the customer was charged, in whole units of the payment's currency. type: - number - 'null' card_brand: description: Card brand, when the customer paid by card. type: - string - 'null' card_last4: description: Last four digits of the card, when the customer paid by card. type: - string - 'null' created_at: description: When the payment was made, as an ISO 8601 timestamp. type: string currency: description: >- Three-letter ISO currency code of the payment. Can differ from the dispute's currency when the processor settles in another currency. type: - string - 'null' id: description: Payment ID, prefixed `pay_`. type: string payment_method_type: description: How the customer paid, such as `card` or `paypal`. type: - string - 'null' payment_processor: description: The processor that handled the payment, such as `stripe`. type: - string - 'null' required: - id - amount - currency - payment_method_type - payment_processor - card_brand - card_last4 - created_at type: object V1ErrorResponse: properties: error: properties: message: description: Human-readable error message. type: string type: description: Machine-readable error code. type: string required: - type - message type: object required: - error type: object DisputeAttachment: properties: content_type: description: The uploaded file's MIME type. type: - string - 'null' filename: description: The uploaded file's name. type: - string - 'null' id: description: >- The attachment's ID. `null` for a Whop-hosted policy, which is not an uploaded file. type: - string - 'null' platform: description: >- Whether this is Whop's own hosted policy, standing in because the seller uploaded none. Sending it back on a PATCH changes nothing. type: boolean url: description: A URL to download the attachment. type: - string - 'null' required: - id - filename - content_type - url - platform type: object responses: InvalidParameters: content: application/json: schema: $ref: '#/components/schemas/V1ErrorResponse' description: Invalid Parameters Unauthorized: content: application/json: schema: $ref: '#/components/schemas/V1ErrorResponse' description: Unauthorized NotFound: content: application/json: schema: $ref: '#/components/schemas/V1ErrorResponse' description: Resource not found securitySchemes: bearerAuth: bearerFormat: auth-scheme description: >- A company API key, company scoped JWT, app API key, or user OAuth token. You must prepend your key/token with the word 'Bearer', which will look like `Bearer ***************************` scheme: bearer type: http ````