This is the documentation for the Ratepay Dispute API. The API is still in development and subject to change. This documentation will evolve as the development of the API progresses.
Dispute OpenAPI Specification (version)
https://api-integration.ratepay.com/dispute/management/
Request
Endpoint to provide evidence for the ITEM_NOT_RECEIVED request for information.
A valid JWT token is required in order to perform requests against this API. See Ratepay Authentication API specification.
For each request, a valid access token must be provided in the Authorization header. See Authentication API for obtaining a valid token.
File with additional evidence. Allowed types are '.zip', '.pdf', '.jpg', '.png', '.gif', '.txt'. Maximum file size is 10 MB.
- Ratepay Integration Platform
https://api-integration.ratepay.com/dispute/management/v1/disputes/{ratepay_dispute_id}/evidences/item-not-received
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://api-integration.ratepay.com/dispute/management/v1/disputes/OpK7rRZP0GND8MobcIKA/evidences/item-not-received \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: multipart/form-data' \
-F 'evidence[ratepay_transaction_id]=scwBgARW-nE93I7_ywhp' \
-F 'evidence[delivery_information][0][carrier_name]=DHL' \
-F 'evidence[delivery_information][0][tracking_number]=2.3834745636235124e+23' \
-F 'evidence[delivery_information][0][status]=PENDING' \
-F 'evidence[delivery_information][0][date]=2019-05-17' \
-F 'evidence[delivery_information][0][address]=Alpenstrasse 21, 15432 DE' \
-F 'evidence[delivery_information][0][note]=string' \
-F additional_evidence=string \
-F file1=stringRequest
Endpoint to provide evidence for the ITEM_RETURNED request for information.
A valid JWT token is required in order to perform requests against this API. See Ratepay Authentication API specification.
For each request, a valid access token must be provided in the Authorization header. See Authentication API for obtaining a valid token.
- Ratepay Integration Platform
https://api-integration.ratepay.com/dispute/management/v1/disputes/{ratepay_dispute_id}/evidences/item-returned
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://api-integration.ratepay.com/dispute/management/v1/disputes/OpK7rRZP0GND8MobcIKA/evidences/item-returned \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: multipart/form-data' \
-F 'evidence[ratepay_transaction_id]=scwBgARW-nE93I7_ywhp' \
-F 'evidence[case_details]=Information regarding the case xyz' \
-F additional_evidence=stringRequest
Endpoint to provide evidence for the DEFEND request for information.
A valid JWT token is required in order to perform requests against this API. See Ratepay Authentication API specification.
For each request, a valid access token must be provided in the Authorization header. See Authentication API for obtaining a valid token.
File with additional evidence. Allowed types are '.zip', '.pdf', '.jpg', '.png', '.gif', '.txt'. Maximum file size is 10 MB.
- Ratepay Integration Platform
https://api-integration.ratepay.com/dispute/management/v1/disputes/{ratepay_dispute_id}/evidences/defend
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://api-integration.ratepay.com/dispute/management/v1/disputes/OpK7rRZP0GND8MobcIKA/evidences/defend \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: multipart/form-data' \
-F 'evidence[ratepay_transaction_id]=scwBgARW-nE93I7_ywhp' \
-F 'evidence[delivery_information][0][carrier_name]=DHL' \
-F 'evidence[delivery_information][0][tracking_number]=2.3834745636235124e+23' \
-F 'evidence[delivery_information][0][status]=PENDING' \
-F 'evidence[delivery_information][0][date]=2019-05-17' \
-F 'evidence[delivery_information][0][address]=Alpenstrasse 21, 15432 DE' \
-F 'evidence[delivery_information][0][note]=string' \
-F additional_evidence=string \
-F file1=stringRequest
Endpoint to provide evidence for the FRAUD request for information.
A valid JWT token is required in order to perform requests against this API. See Ratepay Authentication API specification.
For each request, a valid access token must be provided in the Authorization header. See Authentication API for obtaining a valid token.
- Ratepay Integration Platform
https://api-integration.ratepay.com/dispute/management/v1/disputes/{ratepay_dispute_id}/evidences/fraud
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://api-integration.ratepay.com/dispute/management/v1/disputes/OpK7rRZP0GND8MobcIKA/evidences/fraud \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: multipart/form-data' \
-F 'evidence[ratepay_transaction_id]=scwBgARW-nE93I7_ywhp' \
-F 'evidence[case_details]=Information regarding the case xyz' \
-F 'evidence[delivery_information][0][carrier_name]=DHL' \
-F 'evidence[delivery_information][0][tracking_number]=2.3834745636235124e+23' \
-F 'evidence[delivery_information][0][status]=PENDING' \
-F 'evidence[delivery_information][0][date]=2019-05-17' \
-F 'evidence[delivery_information][0][address]=Alpenstrasse 21, 15432 DE' \
-F 'evidence[delivery_information][0][note]=string' \
-F additional_evidence=string \
-F file1=string