Skip to main content
POST
Create connection
Create a new connection (BringinLink). Returns immediately with INITIATING status (HTTP 202). The standing order is created asynchronously — poll GET /bringin-link/{id} every 2-3 seconds to track progress. Requires a per-user api-key.
Always call GET /bringin-link first to check for existing connections. Creating a duplicate returns a 409 error. See best practices.
name
string
required
User-facing label (2-50 chars). Must be unique per user across active connections.
type
string
required
FIAT_TO_CRYPTO or CRYPTO_TO_FIAT
subtype
string
required
ONCHAIN or LN (Lightning is only supported for CRYPTO_TO_FIAT)
destinationAddress
string
Crypto address (26-90 chars). Required for FIAT_TO_CRYPTO unless whitelistedAddressId is provided.
destinationCurrency
string
default:"BTC"
Target crypto: BTC, ETH, USDC, USDT, or POL. For FIAT_TO_CRYPTO only.
network
string
Blockchain network. Required for FIAT_TO_CRYPTO. Must be compatible with destinationCurrency:
  • BTC: BTC
  • ETH: ETH
  • USDC: USDC (Ethereum) or POLYGON
  • USDT: USDT (Polygon) or ETH (Ethereum)
  • POL: POL or POLYGON
sourceCurrency
string
default:"BTC"
Source crypto for CRYPTO_TO_FIAT + ONCHAIN. Options: BTC, ETH, USDC.
beneficiary
object
Bank account details. Required for CRYPTO_TO_FIAT unless beneficiaryId is provided.
beneficiaryId
string
UUID of an existing beneficiary. Use instead of beneficiary object. The IBAN is auto-whitelisted if needed.
lnAddress
string
Lightning address username (3-30 chars, lowercase alphanumeric + _/-, no consecutive specials). Required for LN subtype. Becomes {username}@bringin.xyz.
whitelistedAddressId
string
Use an existing whitelisted address instead of destinationAddress.

After creation

Poll GET /bringin-link/{id} every 2-3 seconds. Typical processing time is 5-15 seconds.
If still INITIATING after 60 seconds, show a timeout message.

Idempotent behaviors

These happen automatically — no client action needed:
  • Existing beneficiary — If the IBAN already exists for this user, the existing beneficiary is reused
  • Existing whitelisted address — If the crypto address is already whitelisted on the same network, it’s reused
  • Standing order reuse (LN only) — If a standing order exists for the same beneficiary, a new LN address points to the existing one