Overview
The Evidence API records, on a transaction already sent to Rapid, the facts that back a defense: terms acceptance, access to the product, delivery confirmation, usage and communication with the customer.
It is an inbound channel: you call Rapid. The record stays attached to the transaction and is used to build the defense when that transaction becomes a dispute.
What it is not
Section titled “What it is not”- It is not file upload. Each evidence item is a JSON record with a 32 KB cap. PDF receipts, screenshots and contracts go in the dashboard’s evidence library, not here.
- It does not create transactions. The transaction must exist beforehand, sent through the Transactions API. If it does not exist, the call returns
404 TRANSACTION_NOT_FOUND.
Flow in short
Section titled “Flow in short”- You send the sale transaction through the Transactions API
- Something that backs the sale happens in your system: the customer accepted the terms, accessed the product, received the delivery
- You record that fact with
POST /evidence, pointing to the transaction - If that transaction becomes a dispute, Rapid uses the records in the defense
Authentication
Section titled “Authentication”Basic Auth with client_id:client_secret, same as the other channels. See Authentication.
Endpoints
Section titled “Endpoints”| Endpoint | What it does |
|---|---|
POST /evidence | Records evidence on a transaction |
GET /evidence | Lists the evidence of a transaction |