Skip to main content
POST
TypeScript

Autorizaciones

Authorization
string
header
requerido

A user OAuth token. Prepend the key or token with Bearer, for example Bearer ***************************. See Auth & API keys for how to get each one.

Scopes

payment:resolution_center_case:manage

Encabezados

Api-Version-Date
string

Pins the request to a dated API version.

Ejemplo:

"2026-11-17"

Idempotency-Key
string

A unique key that makes this request safe to retry. See Idempotent requests.

Maximum string length: 255
Ejemplo:

"d9105228-4a08-46b1-8b91-42fed586d383"

Parámetros de ruta

id
string
requerido

The resolution center case ID (reso_ tag).

Cuerpo

application/json
message
string
requerido

Why you are appealing the decision.

Ejemplo:

"The coating is already flaking on the hood two weeks later."

attachments
object[]

Up to 3 evidence files, by existing file id or direct_upload_id.

Respuesta

case appealed

account
object | null
requerido

The account the case was filed against.

amount
number
requerido

The amount in question, in whole units of currency.

Ejemplo:

249

available_actions
enum<string>[]
requerido

What you can do to this case right now, named for the endpoint that does it. Resolved for the calling credential, so a merchant and a customer reading the same case see their own options.

Opciones disponibles:
accept,
deny,
request_info,
reply,
appeal,
withdraw
buyer
object
requerido

The customer who opened the case.

created_at
string
requerido

When the case was opened, as an ISO 8601 timestamp.

Ejemplo:

"2026-01-01T12:00:00.000Z"

currency
string | null
requerido

Three-letter ISO currency code of the amount.

Ejemplo:

"usd"

customer_appealed
boolean
requerido

Whether the customer has appealed a decision on this case.

Ejemplo:

false

escalated
boolean
requerido

Whether Whop is involved — either reviewing the case, or waiting on the side named by status for something it asked for while reviewing.

Ejemplo:

false

id
string
requerido

Resolution center case ID, prefixed reso_.

Ejemplo:

"reso_xxxxxxxxxxxxxx"

line_items
object[]
requerido
outcome
enum<string> | null
requerido

Who prevailed on the claim. null until the case closes. Read refund for whether any money actually moved.

Opciones disponibles:
customer_won,
merchant_won,
withdrawn,
null
Ejemplo:

"merchant_won"

payment
object
requerido

The payment the case was opened against.

product_id
string | null
requerido

The product the payment was for, prefixed prod_.

Ejemplo:

"prod_xxxxxxxxxxxxxx"

reason
enum<string>
requerido

What the customer says went wrong. Shares the /disputes vocabulary, so a case that later becomes a chargeback reports the same complaint.

Opciones disponibles:
fraudulent,
product_not_received,
not_as_described,
product_unacceptable,
subscription_canceled
Ejemplo:

"product_not_received"

refund
enum<string> | null
requerido

Whether money moved and off whose balance: none, merchant, or platform (Whop refunded the customer and the merchant kept the funds). Independent of outcome — a case the merchant won can still carry a platform refund. null while the case is open, and on older closed cases that predate this being recorded.

Opciones disponibles:
none,
merchant,
platform,
null
Ejemplo:

"none"

response_due_at
string | null
requerido

When the next response is due, as an ISO 8601 timestamp.

Ejemplo:

"2026-01-01T12:00:00.000Z"

status
enum<string>
requerido

Who the case is waiting on. awaiting_merchant and awaiting_customer name the side that owes a response, under_review means Whop is deciding, and closed means it is settled — read outcome for how.

Opciones disponibles:
awaiting_merchant,
awaiting_customer,
under_review,
closed
Ejemplo:

"closed"

updated_at
string
requerido

When the case was last changed, as an ISO 8601 timestamp.

Ejemplo:

"2026-01-01T12:00:00.000Z"

variant_id
string | null
requerido

The variant the payment was made on, prefixed plan_.

Ejemplo:

"plan_xxxxxxxxxxxxxx"