Skip to main content
POST
Create contact

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

x-api-key
string | null

Body

application/json

Request to create a contact.

name
string
default:""
Required string length: 1 - 200
currency
string | null

Currency override

Required string length: 3 - 4
email
string | null
crypto
ContactCryptoInput · object | null

Crypto contact input.

account
OnchainAccountInput · object

Onchain wallet contact input.

iban
IBANAccountDetails · object

IBAN (SEPA) external account.

address
UserAddress · object | null

Address schema for user.

Canonical field names: street_address, address_line_2, city, state, country, zip. Accepts legacy Align/IBAN field names (street_line_1, street_line_2, postal_code) for backward compatibility with existing JSONB data.

relationship
enum<string> | null

How a payout contact relates to the user.

The vocabulary mirrors Swipelux's recipient relationships so the common values project onto their API unchanged, but this is our own domain type: SELF marks a first-party payout to the user's own account at another bank and has no Swipelux counterpart. Providers own that projection — see SwipeluxRecipients._recipient_relationship — so nothing here depends on a provider, and no provider enum has to carry a value it cannot accept.

Available options:
employee,
contractor,
vendor,
subsidiary,
merchant,
customer,
landlord,
family,
other,
self

Response

Successful Response