subotiz-com 争议 API

The 争议 API from subotiz-com — 2 operation(s) for 争议.

Operations 2

GET /api/v1/disputes List disputes #
GET /api/v1/disputes/{dispute_id} Get dispute details #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/subotiz-com:subotiz-com-default-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

subotiz-com-default-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Subotiz Com 争议 API
  version: 1.0.0
  description: 'Operations tagged 争议 across 2 of this provider''s published API definitions: subotiz-com-openapi.yml, v1-en.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://{api}.subotiz.com
  variables:
    api:
      default: api
security:
- sec0: []
tags:
- name: 争议
paths:
  /api/v1/disputes:
    get:
      tags:
      - 争议
      summary: List disputes
      description: List disputes with filtering and pagination
      operationId: v1-dispute-list-dispute
      parameters:
      - name: ids
        in: query
        description: Filter by Subotiz dispute IDs
        schema:
          type: array
          items:
            type: string
      - name: channel_dispute_ids
        in: query
        description: Filter by channel dispute IDs
        schema:
          type: array
          items:
            type: string
      - name: order_ids
        in: query
        description: Filter by order IDs
        schema:
          type: array
          items:
            type: string
      - name: dispute_status
        in: query
        description: Dispute status filter, comma separated values, e.g. `needs_response,under_review`
        schema:
          type: array
          items:
            type: string
      - name: payment_channel
        in: query
        description: Payment channel filter, comma separated values
        schema:
          type: array
          items:
            type: string
      - name: dispute_reason
        in: query
        description: Dispute reason filter, comma separated values
        schema:
          type: array
          items:
            type: string
      - name: starting_after
        in: query
        description: 'Cursor for pagination: starting_after'
        schema:
          type: string
      - name: ending_before
        in: query
        description: 'Cursor for pagination: ending_before'
        schema:
          type: string
      - name: limit
        in: query
        description: Page size, default 10, range [1,100]
        schema:
          type: integer
          format: int32
      - name: merchant_id
        in: query
        description: Merchant ID
        schema:
          type: string
      - name: created_at.gt
        in: query
        description: Minimum value to filter by (exclusive, UTC time in RFC3339 format, such as '2025-01-01T00:00:00Z')
        schema:
          type: string
      - name: created_at.gte
        in: query
        description: Minimum value to filter by (inclusive, UTC time in RFC3339 format, such as '2025-01-01T00:00:00Z')
        schema:
          type: string
      - name: created_at.lt
        in: query
        description: Maximum value to filter by (exclusive, UTC time in RFC3339 format, such as '2025-01-01T00:00:00Z')
        schema:
          type: string
      - name: created_at.lte
        in: query
        description: Maximum value to filter by (inclusive, UTC time in RFC3339 format, such as '2025-01-01T00:00:00Z')
        schema:
          type: string
      - name: updated_at.gt
        in: query
        description: Minimum value to filter by (exclusive, UTC time in RFC3339 format, such as '2025-01-01T00:00:00Z')
        schema:
          type: string
      - name: updated_at.gte
        in: query
        description: Minimum value to filter by (inclusive, UTC time in RFC3339 format, such as '2025-01-01T00:00:00Z')
        schema:
          type: string
      - name: updated_at.lt
        in: query
        description: Maximum value to filter by (exclusive, UTC time in RFC3339 format, such as '2025-01-01T00:00:00Z')
        schema:
          type: string
      - name: updated_at.lte
        in: query
        description: Maximum value to filter by (inclusive, UTC time in RFC3339 format, such as '2025-01-01T00:00:00Z')
        schema:
          type: string
      - $ref: '#/components/parameters/HeaderRequestID'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListDisputesResponse'
        '422':
          description: merchant_id is required
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
              example:
                code: InvalidParameter
                message: merchant_id is required.
    servers:
    - url: https://{api}.subotiz.com
      variables:
        api:
          default: api
  /api/v1/disputes/{dispute_id}:
    get:
      tags:
      - 争议
      summary: Get dispute details
      description: Retrieve a single dispute by ID
      operationId: v1-dispute-get-dispute
      parameters:
      - name: dispute_id
        in: path
        description: Subotiz dispute ID or channel dispute ID
        required: true
        schema:
          type: string
      - name: merchant_id
        in: query
        description: Merchant ID
        schema:
          type: string
      - $ref: '#/components/parameters/HeaderRequestID'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetDisputeResponse'
        '422':
          description: merchant_id is required
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
              example:
                code: InvalidParameter
                message: merchant_id is required.
    servers:
    - url: https://{api}.subotiz.com
      variables:
        api:
          default: api
components:
  parameters:
    HeaderRequestID:
      name: Request-Id
      in: header
      description: The unique identifier of the request
      required: true
      schema:
        type: string
        default: 008e3967-a1b5-48bb-be14-d5bff5092e61
  schemas:
    Dispute:
      type: object
      properties:
        id:
          type: string
          description: Subotiz dispute ID
        channel_dispute_id:
          type: string
          description: Channel dispute ID
        merchant_id:
          type: string
          description: Merchant ID
        order_id:
          type: string
          description: Order ID
        payment_channel:
          type: string
          description: Payment channel
        payment_method:
          type: string
          description: Payment method
        dispute_status:
          type: string
          description: 'Dispute status:

            - inquiry_needs_response - merchant needs to respond (inquiry)

            - inquiry_under_review - under review (inquiry)

            - case_closed - case closed

            - needs_response - merchant needs to respond

            - under_review - under review

            - won - dispute won

            - lost - dispute lost

            - open - unresolved

            - pending_customer_response - pending customer response

            - needs_response_appealable - merchant needs to respond (appealable)'
        dispute_reason:
          type: string
          description: 'Dispute reason:

            - unauthorized

            - product_not_received

            - product_unacceptable

            - credit_not_processed

            - duplicate

            - subscription_canceled

            - unrecognized

            - incorrect_charge_amount

            - payment_by_other_methods

            - remittance_processing_error

            - others'
        order_amount:
          type: string
          description: Order amount
        order_currency:
          type: string
          description: Order currency
        dispute_amount:
          type: string
          description: Dispute amount
        dispute_currency:
          type: string
          description: Dispute currency
        dispute_create_time:
          type: string
          description: Dispute creation time
        dispute_update_time:
          type: string
          description: Last update time
        dispute_due_time:
          type: string
          description: Response due time
    ListDisputesResponse:
      type: object
      properties:
        code:
          type: string
          description: error code
        message:
          type: string
          description: error message
        data:
          $ref: '#/components/schemas/ListDisputesResponse_Data'
    GetDisputeResponse:
      type: object
      properties:
        code:
          type: string
          description: error code
        message:
          type: string
          description: error message
        data:
          $ref: '#/components/schemas/GetDisputeResponse_Data'
    GetDisputeResponse_Data:
      type: object
      properties:
        id:
          type: string
          description: Subotiz dispute ID
        channel_dispute_id:
          type: string
          description: Channel dispute ID
        merchant_id:
          type: string
          description: Merchant ID
        order_id:
          type: string
          description: Order ID
        payment_channel:
          type: string
          description: Payment channel
        payment_method:
          type: string
          description: Payment method
        dispute_status:
          type: string
          description: 'Dispute status:

            - inquiry_needs_response - merchant needs to respond (inquiry)

            - inquiry_under_review - under review (inquiry)

            - case_closed - case closed

            - needs_response - merchant needs to respond

            - under_review - under review

            - won - dispute won

            - lost - dispute lost

            - open - unresolved

            - pending_customer_response - pending customer response

            - needs_response_appealable - merchant needs to respond (appealable)'
        dispute_reason:
          type: string
          description: 'Dispute reason:

            - unauthorized

            - product_not_received

            - product_unacceptable

            - credit_not_processed

            - duplicate

            - subscription_canceled

            - unrecognized

            - incorrect_charge_amount

            - payment_by_other_methods

            - remittance_processing_error

            - others'
        order_amount:
          type: string
          description: Order amount
        order_currency:
          type: string
          description: Order currency
        dispute_amount:
          type: string
          description: Dispute amount
        dispute_currency:
          type: string
          description: Dispute currency
        dispute_create_time:
          type: string
          description: Dispute creation time
        dispute_update_time:
          type: string
          description: Last update time
        dispute_due_time:
          type: string
          description: Response due time
    BaseResponse:
      type: object
      properties:
        code:
          type: string
          description: error code
        message:
          type: string
          description: error message
    ListDisputesResponse_Data:
      type: object
      properties:
        has_more:
          type: boolean
          description: Whether there is a next page
        list:
          type: array
          items:
            $ref: '#/components/schemas/Dispute'
          description: List of disputes
  securitySchemes:
    sec0:
      type: http
      description: 'Bearer API Key authentication. Format: Authorization: Bearer {your_api_key}'
      scheme: bearer
x-refined-from:
- subotiz-com-openapi.yml
- v1-en.yaml