Create a destination
Save bank instructions on a contact. Use the returned destination id in the matching per-rail transfer create endpoint.
Authorizations
User API key authentication. Create a key under Settings → API keys in the Slash dashboard (https://app.slash.com/global-settings/api-keys) and send the x-legal-entity header naming the legal entity to act on with every request. Keys scoped to a legal entity are rejected with 403 user_api_key_required.
Headers
Unique caller-generated key for one create request. Once an authenticated, schema-valid request reaches the operation, the key is permanently consumed for that operation and legal entity whether the operation succeeds or fails. Reusing it in that scope returns 409 and never replays a response, unlike API v1, which replays the original response for a matching key.
1 - 255The legal entity to act on. Required on every request; a user API key can act on any legal entity its user has access to.
^le_[a-zA-Z0-9]+$Body
- US bank account
- International bank account
Save US routing and account details for ACH, wire, or realtime payments.
Contact id with the le_c_ prefix.
bank_account 1 - 2551 - 34^[0-9]{9}$checking, savings Response
The created destination.
- DestinationBankAccount
- DestinationInternationalWire
US routing and account details usable for ACH, wire, or realtime payments.
Destination id with the le_contact_destination_ prefix.
Contact that owns this destination.
Display name visible to your organization.
active, pending, disabled, archived ach, wire, realtime, international_wire bank_account