BlockRiver AG is a member of VQF, membership number 101302. Regulatory information

--:-- Zurich

Launch Desk Begin onboarding

API connectivity

One API for accounts, payments, trading and custody.

Build BlockRiver into your own systems. Use the whole platform or only the modules you need: named accounts and payments first, with OTC execution, custody and reporting alongside.

Begin onboarding API documentation
Connection diagram: your system on the left, one connection plate marked A, and five platform modules numbered one to five: accounts, payments, trading, custody and reporting.YOUR SYSTEMONE CONNECTIONA12345
Fig. 1. Connection diagram. Your system, one connection (A) and the five modules behind it.

  1. The connection

    REST for operations, WebSocket for events, FIX for trading.

  2. Accounts

    Named accounts and IBANs, balances.

  3. Payments

    In and out, with FX conversion.

  4. Trading

    Indicative and firm prices, RFQ, execution.

  5. Custody

    Wallets, positions, approval workflows.

  6. Reporting

    Statements and post-trade reports.

Sheet
B-06 · API
Drawing
Connection diagram
Scale
Not to scale
Status
Current

Four ways to integrate.

The API reaches the same platform clients use through Launch Desk. Integrate the full stack, or only the layer you are missing.

  1. 01

    Unified banking

    Multi-currency accounts and named IBANs inside your own product.

    • Account and IBAN issuance
    • Incoming and outgoing payments
    • FX conversion
    • Statements and reporting
  2. 02

    Embedded OTC desk

    The complete stack as the back end for pricing, trading, settlement and reporting.

    • Pricing and quoting
    • Trade lifecycle
    • Account, wallet and IBAN management
    • Settlement and reconciliation
  3. 03

    Execution-only liquidity

    Only the execution layer, for large tickets, alongside your existing banking relationships.

    • Indicative and firm pricing
    • RFQ and RFS flows
    • Trade execution
    • Post-trade reporting
  4. 04

    Digital-asset custody

    Segregated digital-asset custody behind your own client-facing systems.

    • Wallet provisioning
    • Balances and positions
    • Cold and warm policy controls
    • Movement initiation and approval

One request, from quote to report.

A conversion through the API runs the same way a trade runs on the desk. Five steps, each one on the audit trail.

  1. Authenticate

    Your system connects with API credentials issued to your company once onboarding is complete.

  2. Quote

    Request an indicative or firm price for a pair and a size.

  3. Execute

    Accept the quote. The trade is filled in a single tranche, against one counterparty.

  4. Settle

    Funds move to the named account or segregated wallet you specify.

  5. Report

    Execution and settlement reports, on request or as events over WebSocket.

IllustrativeNot a real endpoint, key or response.
# 2. Ask for a firm quote
POST /quotes
{
  "sell":   "EUR",
  "buy":    "USDC",
  "amount": "250000.00",
  "type":   "firm"
}

# The reply: one price for the whole amount
{
  "quote_id":   "q_example",
  "price":      "<rate>",
  "valid_until": "<timestamp>"
}

# 3. Accept it, and name where it settles
POST /quotes/q_example/accept
{ "settle_to": "<your named account>" }
  1. REST

    For primary operations

    Accounts, payments, quotes, trades and custody instructions.

  2. WS

    WebSocket for events

    Prices, payment and trade status as they change.

  3. FIX

    For standard trading messages

    For desks that already speak FIX.

  4. CTRL

    Controls built in

    Idempotent endpoints, full audit trails, structured errors, event sequencing, role-based controls and supervised movement policies.

What you can build.

Payments lead. Most integrations start with accounts and payouts, and add conversion or custody later.

  1. 01

    Accounts inside your product

    Named multi-currency accounts and IBANs for your clients, with payments in and out, under your own interface.

    Neobanks
  2. 02

    Collections and payouts

    Receipts and payouts in GBP, EUR, CHF, USD and AED, triggered from your own systems and reconciled against your ledger.

    Remittance providers
  3. 03

    Fiat and stablecoin conversion

    On-ramp and off-ramp flows priced and settled by API, for payment operators that need a counterparty rather than an exchange.

    Payment companies
  4. 04

    Block execution for your clients

    Route large tickets to the OTC desk without building trading infrastructure of your own.

    Introducing brokers
  5. 05

    Custody behind your front end

    Segregated wallets and positions for each of your clients, instructed from your own systems.

    Custody

From onboarding to first settlement.

Four steps, from KYB to your first settlement. Our engineering team works with yours through each one.

  1. Fig. 2a. The file.

    Onboard

    Your company completes KYB, as every BlockRiver client does.

  2. Fig. 2b. A dashed line: the sandbox.

    Scope and sandbox

    Choose the modules you need, then build against a sandbox before anything real moves.

  3. Fig. 2c. The line, tested.

    Test

    Run your flows end to end. Test trades confirm routing and reconciliation before production.

  4. Fig. 2d. Live, and the first settlement.

    Go live

    Production access, then your first settlement into a named account.

Tell us what you want to build.

Begin onboarding Discuss with us Or run the platform under your brand