> ## Documentation Index > Fetch the complete documentation index at: https://docs.shoply.gg/llms.txt > Use this file to discover all available pages before exploring further. # Mark a dispute as answered > Says the store answered a dispute in its provider's own dashboard (PayPal's Resolution Center, Revolut, Adyen, Whop, Shopify), which Shoply cannot send to. It then reads as under review, and its answer can no longer change. 409 `not_answerable` where it is not waiting on an answer there. Needs the `disputes.write` permission (Answer Disputes). ## OpenAPI ````yaml /api-reference/openapi.json post /stores/{storeId}/disputes/{disputeId}/mark-submitted openapi: 3.1.0 info: title: Shoply API version: '1' description: >- Everything a store's own server can do with a secret API key: its catalogue, orders, customers, marketing, finance and the rest of what the dashboard does. And the Customer API, which a buyer's own device asks with a token of theirs. servers: - url: https://api.shoply.gg/v1 security: - apiKey: [] tags: - name: API key - name: Store - name: Domain - name: Payment methods - name: Analytics - name: Storefronts - name: Storefront code - name: Payment Routing - name: Custom payment methods - name: Products - name: Product pictures - name: Stock - name: Categories - name: Upsells - name: Subscriptions - name: Orders - name: Invoices - name: Reviews - name: Coupons - name: Coupon categories - name: Coupon pop-up - name: Sales - name: Blog - name: Search settings - name: Redirects - name: Sitemap - name: Cart Recovery - name: Email Marketing - name: Email Templates - name: Customers - name: Affiliates - name: Support Tickets - name: Blacklist - name: Fraud protection - name: Disputes - name: Finance - name: Tax - name: Expenses - name: Expense setup - name: API requests - name: Webhook endpoints - name: Webhook deliveries - name: Customer API paths: /stores/{storeId}/disputes/{disputeId}/mark-submitted: post: tags: - Disputes summary: Mark a dispute as answered description: >- Says the store answered a dispute in its provider's own dashboard (PayPal's Resolution Center, Revolut, Adyen, Whop, Shopify), which Shoply cannot send to. It then reads as under review, and its answer can no longer change. 409 `not_answerable` where it is not waiting on an answer there. Needs the `disputes.write` permission (Answer Disputes). operationId: disputes.markSubmitted parameters: - name: storeId in: path required: true description: >- The store's ID. A key reaches the store it was made in: `GET /key` answers which. schema: type: string - name: disputeId in: path required: true description: The dispute, by its ID. schema: type: string - $ref: '#/components/parameters/IdempotencyKey' responses: '200': description: It worked. content: application/json: schema: type: object properties: success: type: boolean message: nullable: true code: nullable: true data: type: object properties: id: type: string orderId: type: string email: type: string provider: type: string providerName: type: string externalId: type: string reason: type: string reasonText: type: string stage: type: string providerStatus: type: string status: type: string amount: type: integer currency: type: string dueAt: type: string answer: type: object properties: state: type: string at: type: string by: type: string note: type: string answeredFrom: type: string answerPlace: type: string accessTaken: type: boolean dateCreated: type: string dateClosed: nullable: true order: type: object properties: id: type: string status: type: string amount: type: integer currency: type: string dateCreated: type: string can: type: object properties: edit: type: boolean submit: type: boolean accept: type: boolean markSubmitted: type: boolean records: type: array items: type: object properties: key: type: string title: type: string facts: type: array items: type: object properties: key: type: string name: type: string value: type: string strong: type: boolean activity: type: - array - object draft: type: object properties: decision: type: string contacted: type: string used: type: string words: type: string saved: type: boolean statement: type: string files: type: - array - object after: type: array items: type: object properties: key: type: string done: type: boolean text: type: string history: type: array items: type: object properties: at: type: string what: type: string detail: type: string example: success: true message: null code: null data: id: 0f8aa05a-52c5-4fc5-8180-36aec2177869 orderId: cc9beefe-9e86-42db-8ef0-354c1ab48b0a email: jonas@example.com provider: paypal providerName: PayPal externalId: PP-D-27803 reason: merchandise_or_service_not_received reasonText: Says it never arrived stage: claim providerStatus: waiting_for_seller_response status: under_review amount: 10 currency: USD dueAt: '2026-10-31T16:20:19Z' answer: state: submitted at: '2026-10-22T16:20:19Z' by: seller note: '' answeredFrom: provider answerPlace: PayPal's Resolution Center accessTaken: false dateCreated: '2026-10-22T16:20:19Z' dateClosed: null order: id: cc9beefe-9e86-42db-8ef0-354c1ab48b0a status: completed amount: 10 currency: USD dateCreated: '2026-10-22T16:20:19Z' can: edit: false submit: false accept: false markSubmitted: false records: - key: buyer title: The Buyer facts: - key: email name: Email value: jonas@example.com strong: false - key: order title: The Order facts: - key: placed name: Placed value: Oct 22, 2026, 4:20 PM UTC strong: false - key: paid name: Paid value: Oct 14, 2026, 4:20 PM UTC · $10.00 · PayPal strong: false activity: [] draft: decision: fight contacted: '' used: '' words: >- The buyer bought Throwaway product (Default) on Oct 14, 2026 and it was delivered at once. saved: false statement: >- The buyer bought Throwaway product (Default) on Oct 14, 2026 and it was delivered at once. What the store's records show: - Email: jonas@example.com - Placed: Oct 22, 2026, 4:20 PM UTC - Paid: Oct 14, 2026, 4:20 PM UTC · $10.00 · PayPal - Delivered: Oct 14, 2026, 4:20 PM UTC · Throwaway product (Default) files: [] after: - key: blacklist done: false text: The buyer is not blacklisted - key: access done: false text: Their keys and files are shown to them history: - at: '2026-10-22T16:20:19Z' what: Answered detail: You marked it as answered in PayPal's Resolution Center. '401': $ref: '#/components/responses/NoKey' '403': $ref: '#/components/responses/NotAllowed' '404': $ref: '#/components/responses/NotFound' '422': $ref: '#/components/responses/Refused' '429': $ref: '#/components/responses/TooMany' x-codeSamples: - lang: javascript label: Node.js source: | import Shoply from "@shoplygg/node"; const shoply = new Shoply({ apiKey: process.env.SHOPLY_API_KEY }); const result = await shoply.disputes.markSubmitted("DISPUTE_ID"); - lang: php label: PHP source: | getenv('SHOPLY_API_KEY')]); $result = $shoply->disputes->markSubmitted('DISPUTE_ID'); - lang: python label: Python source: | import shoply client = shoply.Client() # reads SHOPLY_API_KEY result = client.disputes.markSubmitted("DISPUTE_ID") components: parameters: IdempotencyKey: name: Idempotency-Key in: header required: false description: >- A word of your own for this one change, up to 180 letters, digits, dots, dashes, underscores and colons. Sent again with the same key, the request is not carried out twice: the first answer comes back, with `Idempotent-Replay: true`. schema: type: string responses: NoKey: description: >- No API key was sent, or the one sent is not a live key: `api_key_required`, `invalid_api_key`. content: application/json: schema: $ref: '#/components/schemas/Refusal' NotAllowed: description: >- The key is real and may not do this: `missing_scope` (with `requiredScope`), `ip_not_allowed`, `account_unavailable`, or `dashboard_only` for something only a person in the dashboard may do. content: application/json: schema: $ref: '#/components/schemas/Refusal' NotFound: description: >- There is no such thing in this store: `not_found`. A store that is not the key's own is answered the same way. content: application/json: schema: $ref: '#/components/schemas/Refusal' Refused: description: >- The request was understood and not carried out. `validation_failed` says what is wrong with each field under `errors`; other codes are the route's own. content: application/json: schema: $ref: '#/components/schemas/Refusal' TooMany: description: >- The key has used up its budget for now: `rate_limited`. `Retry-After` says how many seconds to wait. content: application/json: schema: $ref: '#/components/schemas/Refusal' schemas: Refusal: type: object properties: success: type: boolean example: false message: type: string description: What is wrong, in words for a person. code: type: string description: What is wrong, as a word that does not change. data: nullable: true errors: type: object description: >- For `validation_failed`: what is wrong with each field, by the field's name. additionalProperties: type: string required: - success - message - code securitySchemes: apiKey: type: http scheme: bearer description: >- A secret API key, made under Developers in the dashboard: `Authorization: Bearer shoply_sk_...` ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.