List Documents for a Dispute

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

If your platform is using a proxy to take SCA-triggering action on behalf of users, you also need to integrate mTLS authentication and use the api-mtls base URL.

Bearer authentication of the form `Bearer <token>`, where token is your auth token. If your platform is using a [proxy](/guides/sca/proxy-management) to take SCA-triggering action on behalf of users, you also need to integrate [mTLS authentication](/guides/sca/platform) and use the `api-mtls` base URL.

Path parameters

ClientIdstringRequired

Platform's API account identifier, associated with the API key.

DisputeIdstringRequired

The unique identifier of the dispute.

Response

Success

Array (Dispute documents)list of objects

The list of dispute documents created by the platform.

1	[
2	{
3	"DisputeId": "159102965",
4	"Type": "DELIVERY_PROOF",
5	"Id": "159188418",
6	"Tag": null,
7	"CreationDate": 1672655973,
8	"ProcessedDate": null,
9	"Status": "VALIDATION_ASKED",
10	"RefusedReasonType": null,
11	"RefusedReasonMessage": null
12	}
13	]