post https://dispute-api-{corename}.{env}.gpsrv.com/addTransactions
Availability
No new clients will be set up with Dispute API 2.0. Legacy clients will eventually be migrated to Dispute API 3.0.
Use the Add Transactions endpoint to attach the transactions that the account holder selects. Specify the transactionId as returned by Get Transactions (which is not the transactionId that you pass to identify a unique endpoint request).
This endpoint is part of a conversational API—a series of endpoint calls that must be made in a certain order. For instructions see the Creating an API 2.0 Dispute guide.
- Previous endpoint: Get Transactions
- Next endpoint: Get Questionnaire
Status codes
See Global Response Statuses for status codes that are common across endpoints.
The table below lists status codes that apply to this specific endpoint.
| Status code | Description |
|---|---|
| 1505-4 | Invalid case ID or case ID returned no results |
| 1505-5 | Invalid request {message} |
| 1505-6 | Error saving case |
| 1505-9 | Unable to resume flow |
| 1505-13 | Case ID references a case that is currently locked |
| 1505-14 | Invalid request message |
| 1505-15 | This case is already resolved with status: {status} |
| 1505-16 | This case has been submitted for processing and this action can no longer be performed. |