curl --request POST \
--url https://platform.swipelux.com/v3/customers/{customerId}/recipients/{recipientId}/destinations \
--header 'Content-Type: application/json' \
--header 'Idempotency-Key: <idempotency-key>' \
--header 'X-API-Key: <api-key>' \
--data '
{
"type": "ach",
"currency": "USD",
"details": {
"routingNumber": "021000021",
"accountNumber": "123456789",
"accountType": "checking",
"bankName": "JPMorgan Chase",
"accountHolderName": "Jason Swipelux",
"country": "US"
}
}
'{
"data": {
"id": "dst_7mA9sL1kBc6dV8xN2pQ4rT",
"type": "ach",
"currency": "USD",
"status": "ready",
"details": {
"routingNumber": "021000021",
"accountNumber": "123456789",
"accountType": "checking",
"bankName": "JPMorgan Chase",
"accountHolderName": "Jason Swipelux",
"country": "US"
},
"createdAt": "2026-06-25T12:01:00.000Z",
"updatedAt": "2026-06-25T12:01:00.000Z",
"archivedAt": null
}
}Add recipient destination
Adds a bank or wallet payout destination to a recipient. Use Accounts for customer-owned destinations.
curl --request POST \
--url https://platform.swipelux.com/v3/customers/{customerId}/recipients/{recipientId}/destinations \
--header 'Content-Type: application/json' \
--header 'Idempotency-Key: <idempotency-key>' \
--header 'X-API-Key: <api-key>' \
--data '
{
"type": "ach",
"currency": "USD",
"details": {
"routingNumber": "021000021",
"accountNumber": "123456789",
"accountType": "checking",
"bankName": "JPMorgan Chase",
"accountHolderName": "Jason Swipelux",
"country": "US"
}
}
'{
"data": {
"id": "dst_7mA9sL1kBc6dV8xN2pQ4rT",
"type": "ach",
"currency": "USD",
"status": "ready",
"details": {
"routingNumber": "021000021",
"accountNumber": "123456789",
"accountType": "checking",
"bankName": "JPMorgan Chase",
"accountHolderName": "Jason Swipelux",
"country": "US"
},
"createdAt": "2026-06-25T12:01:00.000Z",
"updatedAt": "2026-06-25T12:01:00.000Z",
"archivedAt": null
}
}Authorizations
Your Swipelux API key. Obtain this from the Swipelux Dashboard.
Headers
Required for effectful v3 requests (POST, PATCH, PUT, DELETE). Reuse the same key with the same body to replay the cached response.
1 - 255Body
Type-specific recipient destination payload. Use top-level Accounts for customer-owned accounts; use recipient destinations when funds land with a recipient relationship.
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
Type-specific recipient destination payload. Use top-level Accounts for customer-owned accounts; use recipient destinations when funds land with a recipient relationship.
Recipient destination type. Closed enum — exhaustive; additions would be a breaking change.
sepa Destination currency for this recipient payout endpoint.
3"USD"
Show child attributes
Show child attributes
Response
Recipient destination created
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9
- Option 10
- Option 11
- Option 12
- Option 13
- Option 14
- Option 15
- Option 16
Show child attributes
Show child attributes