Archive Recipient
Ramping — Recipients
Archive Recipient
POST /v1/ramp/recipients//archive — Archive a recipient
POST
Archive Recipient
Documentation Index
Fetch the complete documentation index at: https://docs.rebelfi.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint:
POST https://api.rebelfi.io/v1/ramp/recipients/{id}/archivePath Parameters
| Field | Type | Required | Description |
|---|---|---|---|
id | integer | Yes | Recipient identifier |
Example Request
Example Response
Response Fields
| Field | Type | Description |
|---|---|---|
id | number | Recipient identifier |
name | string | Recipient name |
type | string | Recipient type |
external_id | string? | Your external reference ID |
kyb_status | string | KYB verification status |
address | object? | Recipient address |
bank_accounts | array | List of linked bank accounts |
onramp_account_count | number | Number of on-ramp accounts |
offramp_account_count | number | Number of off-ramp accounts |
total_volume_usd | string | Total volume in USD |
transaction_count | number | Total number of transactions |
created_at | string | Creation timestamp (ISO 8601) |
archived_at | string | Archive timestamp (ISO 8601) |
Archiving is a soft delete. The recipient and its data are preserved but the recipient cannot be used for new operations.