1. Crypto Withdrawals
Partner API
  • Getting Started
    • Introduction
    • Authentication
    • Business Use Cases
  • API References
    • Balances & History
      • Get Balances
      • Get Balance History
    • Crypto Deposits
      • Get Crypto Deposit Details
      • Add Travel Rule
    • Crypto Withdrawals
      • Get Whitelisted Wallets
        GET
      • Add Whitelisted Wallet
        POST
      • Delete Whitelisted Wallet
        DELETE
      • Create Crypto Withdrawal
        POST
      • Get Crypto Withdrawal Details
        GET
    • SEPA Deposits
      • Get SEPA Payment Details
      • Get SEPA Deposit Details
    • SEPA Withdrawals
      • Create SEPA Withdrawal
      • Get SEPA Withdrawal Details
    • Currency Exchange
      • Get Rates
      • Create Lock
      • Create Exchange
      • Get Exchange Details
  • Integration
    • Integration Guides
    • Transaction Processing
    • Error Handling
    • Rate Limiting
    • Webhooks
      • Crypto Deposit Webhook
      • Crypto Withdrawal Webhook
      • SEPA Deposit Webhook
      • SEPA Withdrawal Webhook
      • Exchange Webhook
  • Reference
    • Supported Currencies
    • Fees
    • FAQ
    • Changelog
    • Support
  1. Crypto Withdrawals

Add Whitelisted Wallet

Testing Env
http://k8s-partnera-partnera-7873f15634-69ebb7c047cac3d1.elb.eu-central-1.amazonaws.com
Testing Env
http://k8s-partnera-partnera-7873f15634-69ebb7c047cac3d1.elb.eu-central-1.amazonaws.com
POST
/v1/partner/whitelisted-wallets
Adds a wallet address to the Partner's withdrawal whitelist. Crypto withdrawals can only be sent to whitelisted addresses.
Recipient details provided here are used for Travel Rule compliance and apply to every withdrawal sent to this address, so they only need to be provided once.

Owner type#

SENDER - the address belongs to the Partner. Requires ownershipDeclaration: true. receiverName is not used.
PRIVATE_INDIVIDUAL - the address belongs to a natural person. Requires receiverName.
BUSINESS - the address belongs to a company. Requires receiverName.

Memo#

Some networks use a memo to identify the recipient at a shared exchange address: XRP (destination tag) and TON (memo/comment). If the recipient provided a memo, it must be included here - without it, funds sent to an exchange may not be credited to the recipient's account. The same address with a different memo is treated as a separate recipient. For other networks, memo is not accepted.
The whitelist is shared with the web interface - addresses added in the web interface are available via the API and vice versa.

Request

Authorization
API Key
Add parameter in header
x-api-key
Example:
x-api-key: ********************
or
Body Params application/jsonRequired

Examples

Responses

🟢201Success
application/json
Wallet address added to the whitelist.
Bodyapplication/json

🟠400P4007: Validation Error
🟠400P4301: Wallet Address Not Valid
🟠400P4302: Wallet Address Already Whitelisted
🟠400P4304: Ownership Declaration Required
🟠401P4001: Missing API Key
🟠401P4002: Invalid API Key
🟠403P4003: IP Not Allowed
🟠403P4004: Access Denied
🔴500P5000: Unknown Error
Request Request Example
Shell
JavaScript
Java
Swift
cURL
curl --location 'http://k8s-partnera-partnera-7873f15634-69ebb7c047cac3d1.elb.eu-central-1.amazonaws.com/v1/partner/whitelisted-wallets' \
--header 'x-api-key: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
    "currency": "DOGE",
    "network": "DOGE",
    "walletAddress": "DC8T55QR88dYbYKjzCBYic8QJ7nhiaJRkx",
    "walletType": "SELF_CUSTODY",
    "ownerType": "PRIVATE_INDIVIDUAL",
    "receiverName": "John Smith"
}'
Response Response Example
201 - Private individual - DOGE
{
    "id": "8cb28fd0-ba0e-445d-8851-13bf1fbfb11d",
    "currency": "DOGE",
    "network": "DOGE",
    "walletAddress": "DC8T55QR88dYbYKjzCBYic8QJ7nhiaJRkx",
    "memo": null,
    "walletType": "SELF_CUSTODY",
    "ownerType": "PRIVATE_INDIVIDUAL",
    "receiverName": "John Smith",
    "createdAt": "2026-10-05T13:24:10.512Z"
}
Previous
Get Whitelisted Wallets
Next
Delete Whitelisted Wallet
Built with