> ## 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. # List resolution center cases > Returns a paginated list of resolution center cases, with optional filtering by company, status, and creation date. Required permissions: - `payment:resolution_center_case:read` ## OpenAPI ````yaml /openapi/api-v1-stable.json get /resolution_center_cases 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-08-1 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: Products name: Products - description: Payments name: Payments - description: Refunds name: Refunds - description: Disputes name: Disputes - description: Dispute alerts name: Dispute alerts - description: Resolution center cases name: Resolution center cases - description: Checkout configurations name: Checkout configurations - description: Setup intents name: Setup intents - description: Payment methods name: Payment methods - description: Invoices name: Invoices - description: Promo codes name: Promo codes - description: Card transactions name: Card transactions - description: Ledger accounts name: Ledger accounts - description: Withdrawals name: Withdrawals - description: Payout methods name: Payout methods - description: Verifications name: Verifications - description: Identity profiles name: Identity profiles - description: Payout accounts name: Payout accounts - description: Topups name: Topups - description: Companies name: Companies - description: Authorized users name: Authorized users - description: Fee markups name: Fee markups - description: Members name: Members - description: Memberships name: Memberships - description: Leads name: Leads - description: Entries name: Entries - description: Shipments name: Shipments - description: Reviews name: Reviews - description: Company token transactions name: Company token transactions - description: Affiliates name: Affiliates - description: Experiences name: Experiences - description: Forums name: Forums - description: Forum posts name: Forum posts - description: Chat channels name: Chat channels - description: Support channels name: Support channels - description: Messages name: Messages - description: Reactions name: Reactions - description: Dm members name: Dm members - description: Dm channels name: Dm channels - description: Notifications name: Notifications - description: Courses name: Courses - description: Course chapters name: Course chapters - description: Course lessons name: Course lessons - description: Course students name: Course students - description: Course lesson interactions name: Course lesson interactions - description: Apps name: Apps - description: Webhooks name: Webhooks - description: App builds name: App builds - description: Access tokens name: Access tokens - description: Account links name: Account links - description: Files name: Files - description: Ai chats name: Ai chats - description: Bounties name: Bounties - description: Stats name: Stats - description: Conversions name: Conversions - description: Ad reports name: Ad reports paths: /resolution_center_cases: get: tags: - Resolution center cases summary: List resolution center cases description: >- Returns a paginated list of resolution center cases, with optional filtering by company, status, and creation date. Required permissions: - `payment:resolution_center_case:read` operationId: listResolutionCenterCase parameters: - explode: true in: query name: after required: false schema: description: >- Returns the elements in the list that come after the specified cursor. type: - string - 'null' style: form - explode: true in: query name: before required: false schema: description: >- Returns the elements in the list that come before the specified cursor. type: - string - 'null' style: form - explode: true in: query name: first required: false schema: description: Returns the first _n_ elements from the list. example: 42 type: - integer - 'null' style: form - explode: true in: query name: last required: false schema: description: Returns the last _n_ elements from the list. example: 42 type: - integer - 'null' style: form - explode: true in: query name: company_id required: false schema: description: >- The unique identifier of the company to list resolution center cases for. example: biz_xxxxxxxxxxxxxx type: - string - 'null' style: form - explode: true in: query name: direction required: false schema: description: The sort direction. oneOf: - $ref: '#/components/schemas/Direction' - type: 'null' style: form - explode: true in: query name: statuses required: false schema: description: Filter by resolution center case status. items: $ref: '#/components/schemas/ResolutionCenterCaseStatuses' type: - array - 'null' style: form - explode: true in: query name: created_before required: false schema: description: Only return cases created before this timestamp. example: '2023-12-01T05:00:00.401Z' format: date-time type: - string - 'null' style: form - explode: true in: query name: created_after required: false schema: description: Only return cases created after this timestamp. example: '2023-12-01T05:00:00.401Z' format: date-time type: - string - 'null' style: form responses: '200': content: application/json: schema: description: The connection type for PublicResolution. properties: data: description: A list of nodes. items: $ref: '#/components/schemas/ResolutionCenterCaseListItem' type: array page_info: $ref: '#/components/schemas/PageInfo' description: Information to aid in pagination. required: - data - page_info type: object description: A successful response '400': content: application/json: example: error: code: parameter_missing message: 'Missing required parameter: amount.' param: amount type: invalid_request_error schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Bad request '401': content: application/json: example: error: message: Invalid or missing API key type: unauthorized schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Unauthorized '403': content: application/json: example: error: message: You do not have permission to access this resource type: forbidden schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Forbidden '404': content: application/json: example: error: message: Resource not found type: not_found schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Not found '422': content: application/json: example: error: null schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Verification required '429': content: application/json: example: error: null schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Too many requests '500': content: application/json: example: error: message: An unexpected error occurred type: internal_server_error schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Internal server error security: - bearerAuth: - payment:resolution_center_case:read components: schemas: Direction: description: The direction of the sort. enum: - asc - desc type: string ResolutionCenterCaseStatuses: description: The statuses a resolution object can have enum: - merchant_response_needed - customer_response_needed - merchant_info_needed - customer_info_needed - under_platform_review - customer_won - merchant_won - customer_withdrew type: string ResolutionCenterCaseListItem: description: >- A resolution center case is a dispute or support case between a user and a company, tracking the issue, status, and outcome. properties: company: description: >- The company involved in this resolution case. Null if the company no longer exists. properties: id: description: The unique identifier for the company. example: biz_xxxxxxxxxxxxxx type: string title: description: The display name of the company shown to customers. example: Pickaxe type: string required: - id - title type: - object - 'null' created_at: description: The datetime the resolution was created. example: '2023-12-01T05:00:00.401Z' format: date-time type: string customer_appealed: description: >- Whether the customer has filed an appeal after the initial resolution decision. type: boolean customer_response_actions: description: The list of actions currently available to the customer. items: $ref: '#/components/schemas/ResolutionCenterCaseCustomerResponses' type: array due_date: description: >- The deadline by which the next response is required. Null if no deadline is currently active. As a Unix timestamp. example: '2023-12-01T05:00:00.401Z' format: date-time type: - string - 'null' id: description: The unique identifier for the resolution. example: reso_xxxxxxxxxxxxx type: string issue: $ref: '#/components/schemas/ResolutionCenterCaseIssueTypes' description: The category of the dispute. merchant_appealed: description: >- Whether the merchant has filed an appeal after the initial resolution decision. type: boolean merchant_response_actions: description: The list of actions currently available to the merchant. items: $ref: '#/components/schemas/ResolutionCenterCaseMerchantResponses' type: array payment: description: The payment record that is the subject of this resolution case. properties: id: description: The unique identifier for the payment. example: pay_xxxxxxxxxxxxxx type: string required: - id type: object status: $ref: '#/components/schemas/ResolutionCenterCaseStatuses' description: >- The current status of the resolution case, indicating which party needs to respond or if the case is closed. updated_at: description: The datetime the resolution was last updated. example: '2023-12-01T05:00:00.401Z' format: date-time type: string user: description: The customer (buyer) who filed this resolution case. properties: id: description: The unique identifier for the user. example: user_xxxxxxxxxxxxx type: string name: description: The user's display name shown on their public profile. example: John Doe type: - string - 'null' username: description: The user's unique username shown on their public profile. example: johndoe42 type: string required: - id - name - username type: object required: - id - status - issue - created_at - updated_at - due_date - customer_appealed - merchant_appealed - customer_response_actions - merchant_response_actions - company - user - payment type: object PageInfo: description: Information about pagination in a connection. properties: end_cursor: description: When paginating forwards, the cursor to continue. type: - string - 'null' has_next_page: description: When paginating forwards, are there more items? type: boolean has_previous_page: description: When paginating backwards, are there more items? type: boolean start_cursor: description: When paginating backwards, the cursor to continue. type: - string - 'null' required: - end_cursor - start_cursor - has_next_page - has_previous_page type: object ResolutionCenterCaseCustomerResponses: description: The types of responses a customer can make to a resolution. enum: - respond - appeal - withdraw type: string ResolutionCenterCaseIssueTypes: description: The different types of issues a resolution can be enum: - forgot_to_cancel - item_not_received - significantly_not_as_described - unauthorized_transaction - product_unacceptable type: string ResolutionCenterCaseMerchantResponses: description: The types of responses a merchant can make to a resolution. enum: - accept - deny - request_more_info - appeal - respond type: string 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 ````