API changelog
Changes to the integration API, newest first. Dashboard-only changes are not listed here.
October 2026: new API
Section titled “October 2026: new API”The current version of the API, replacing the one from the previous system. If you already integrated with Rapid, this is the list of what changes.
- Transactions API at
/api/v1/transactions: create, send in batch (up to 1000 per call), retrieve by Rapid’s ID or by your system’s ID, update and delete. - List merchants, to find the
merchant_idthrough the API. - List alerts with filters (status, dates, card, provider ID) and pagination.
- Update status of the alert at
PATCH /api/v1/chargeback-alert/alerts/:id/status. v2webhook format: delivery signed with HMAC-SHA256 and a timestamp, event identified in the body and in a header, and a single channel for every product.- Evidence and Capture, which feed the Dispute defense.
- A single error format across the whole API (see Response codes).
- Developer tools: the documentation in your AI assistant (MCP), in Markdown and in
llms.txt, and the Postman collection.
Changed
Section titled “Changed”- Webhook only over HTTPS and to a public internet address. A redirect that turns the POST into a GET (
301,302,303) is not followed. See Retries and logs. - Request limit per IP, also counting
401responses, withRetry-Afteron the429. See Response codes. - Webhook retries at defined intervals. See Retries and logs.
Still works, from the previous system
Section titled “Still works, from the previous system”Kept for those who already integrated, with no change on your side. For a new integration, use the endpoints in the right column.
| From the previous system | Use in a new integration |
|---|---|
POST /chargeback-alert/update/status | PATCH /api/v1/chargeback-alert/alerts/:id/status |
POST /chargeback-alert/get | GET /api/v1/chargeback-alert/alerts |
Webhook in the legacy format, with clientid/clientkey | Webhook in the v2 format, with a signature |
These old endpoints will be removed once there are no more calls to them.
No equivalent
Section titled “No equivalent”The previous system’s Transactions API (/transactions/create, /transactions/update and /transactions/delete, without /api/v1) does not exist in the new API. The path and the fields changed: the integration needs to move to the new Transactions API.