GuidesAPI ReferenceChangelog
API Reference

Create Auto-Conversion Rule

Create an Auto-Conversion Rule for fiat->crypto, crypto->fiat, or crypto->crypto conversions.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Supported Assets:

  • USD, USDC, USDT, PYUSD, RLUSD, USDG, USDP, EURC, MXNB
    Supported Networks:
  • Fiat deposit networks: US_FEDWIRE, SWIFT
  • Crypto networks: ETHEREUM, POLYGON, BASE, ARBITRUM, AVALANCHE, BNBCHAIN, SOLANA, TRON

Validation Rules:

  • Supported pairs: fiat->crypto, crypto->fiat, and crypto->crypto; fiat->fiat is NOT supported
  • Idempotency-Key header is required and must be a valid UUID v4
  • Source network must match asset type (fiat asset requires fiat network, crypto asset requires crypto network)
  • For crypto withdrawal destination: network is required when wallet_address is provided
  • For fiat destination: network will be omitted
  • For a crypto-to-fiat bank payout that requires a local payment code, set destination.code to the applicable value from the Local Payment Code guide

Withdrawal Configuration:

  • Fiat-to-Crypto or Crypto->Crypto with withdrawal: provide wallet_address (external crypto wallet address)
  • Crypto-to-Fiat with withdrawal: provide external_account_id (bank account ID from external-accounts API)
  • Conversion-only (no withdrawal): omit both fields, converted funds remain in customer's account

Idempotency & Webhook Behavior:

  • This endpoint provisions resources asynchronously. A rule-creation webhook may arrive before the HTTP response.
  • Reusing an existing Idempotency-Key returns 409 Conflict. Use Get Auto-Conversion Rule by Idempotency Key to retrieve the rule after a duplicate request, timeout, or webhook.
  • Correlate the response and webhook with the creation key, then retrieve the rule to check its current status and deposit information.

Response & Status:

  • The create response returns the rule's current status. It may still be PENDING, or asynchronous provisioning may already have advanced it.
  • The create response omits deposit_info_status and source_deposit_info, even if the returned rule is already ACTIVE.
  • Retrieve the rule to get deposit information. Only fund it when deposit_info_status=ACTIVE and source_deposit_info is present. Rule status=ACTIVE alone does not establish that deposit information is available.
Path Params
string
required

Customer ID (UUID format)

Body Params

Request body for creating a new Auto-Conversion Rule.

source
object
required

Source asset and network configuration.

  • For a fiat source, use a bank network such as US_FEDWIRE or SWIFT
  • For a crypto source, use a blockchain network such as ETHEREUM or POLYGON
destination
object
required

Destination asset and optional withdrawal configuration.

  • For crypto withdrawal destination: network is required when wallet_address is provided
  • For fiat destination: network should be omitted
  • wallet_address: for fiat->crypto or crypto->crypto withdrawal to external wallet
  • external_account_id: for crypto->fiat withdrawal to bank account
Headers
string
required

Required UUID v4. Reusing a key for this customer returns 409. Retrieve the existing Auto-Conversion Rule by its idempotency key.

Responses

Language
Credentials
Bearer
OneMoney-HMAC-SHA256
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json