Sign in
fixed-routes

Validate if a fixed route can be created

Checks if a fixed route configuration is valid before creating it. Returns validation result with any errors.

post/v1/fixed-routes/validate

Headers

X-API-Keystring

API key

Request body

sweepTargetAccountIdstring required

The destination account ID for the fixed route

fixedRouteType'FIAT_TO_CRYPTO' | 'CRYPTO_TO_FIAT' | 'CRYPTO_TO_CRYPTO' | 'FIAT_TO_CRYPTO_TO_FIAT' required

The type of fixed route to create

sourceRailstring

Source rail - payment rail for incoming deposits (e.g., ACH, WIRE, SEPA)

sourceCurrencystring

Source currency for deposits (e.g., USD, EUR)

destinationRailstring

Destination rail - chain/network for outgoing sweep (e.g., BASE, ETHEREUM)

destinationCurrencystring

Destination currency to convert to (e.g., USDC, USDT)

braleAutomationIdstring

Bound Brale wire automation ID for legacy onramp routes. Omit for new standby-pool routes (Solana SBC intermediary).

Example request

{
  "sweepTargetAccountId": "ewa_abc123",
  "fixedRouteType": "FIAT_TO_CRYPTO",
  "sourceRail": "ACH",
  "sourceCurrency": "USD",
  "destinationRail": "BASE",
  "destinationCurrency": "USDC"
}

Response

Validation result

validboolean required

Whether the fixed route configuration is valid

errorstring

Error message if validation failed

Example response

{
  "valid": true,
  "error": "FIAT_TO_CRYPTO route requires a wallet as sweep target",
  "minimumAmount": {
    "currency": "USD",
    "exponent": 2,
    "value": "12345",
    "displayValue": "123.45"
  }
}

Changes

No recorded changes to this endpoint across all 1 revision of this API.