code Developer Hub

Build the future of money with Bridflow

Documentation, SDKs, and tools to integrate Fiat and Web3 payments in minutes.

Cmd + K

Suggestions:

Your first API flow in 3 steps

Start with the current OpenAPI contract: authenticate, create an account, and continue with KYC status polling.

index.js

API request preview

Build a current transfer route request

Preview the PATCH /transfers/info/v1 body and response shape from the current OpenAPI contract.

tune Configure Request

Endpoint

PATCH PATCH /transfers/info/v1

Source currency

Source rail

Destination asset

Destination rail

Response

route Generate a response preview from the selected route.

OpenAPI specification, always up to date

Our API is fully described using the OpenAPI (Swagger) standard, ensuring predictable, secure, and easy-to-maintain integrations.

Build on a solid foundation

fact_check

Single source of truth

The specification defines exactly which endpoints exist and what data they expect, eliminating guesswork and errors.
code_blocks

Autogenerated SDKs

Generate strongly-typed API clients for Node.js, Python, Go, PHP, and many more languages.
integration_instructions

Interactive Documentation

Explore, visualize, and test our endpoints directly from the interactive UI (compatible with Swagger UI).
rule

Validation and Mocks

Accelerate development using mock servers based on our specification before connecting your real code.
api

Native import

Import the entire collection directly into Postman, Insomnia, or API tools securely and easily.

terminal terminal OpenAPI v3

// Example Request (cURL)

curl -X PATCH "https://api-preview.bridflow.com/transfers/info/v1" \
  -H "Authorization: Bearer ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "selectedSource": {
      "currency": "Eur",
      "paymentRail": "Sepa",
      "provider": "Bridge"
    },
    "selectedDestination": {
      "currency": "Usdc",
      "paymentRail": "Polygon",
      "provider": "Bridge"
    }
  }'

// Response defined by OpenAPI

{
  "selectedSource": {
    "currency": "Eur",
    "paymentRail": "Sepa",
    "provider": "Bridge"
  },
  "selectedDestination": {
    "currency": "Usdc",
    "paymentRail": "Polygon",
    "provider": "Bridge"
  },
  "availableSources": [],
  "availableDestinations": [],
  "routes": [
    {
      "routeKey": "Sepa:Eur->Polygon:Usdc",
      "flowType": "AutoForwarding",
      "provider": "Bridge"
    }
  ],
  "transactionsInfo": []
}

Ready to integrate? Open live API reference arrow_forward

Robust authentication and strict error handling

Built on industry standards to ensure the security of your funds and the stability of your integration.

verified_user

Basic credentials and Bearer tokens

Use Basic authentication only to create a current connect token, then send Bearer-authenticated API calls from your backend.

lock_open

1. Token Generation

POST /identity/auth/tokens/current/v1 returns an access_token for API calls.

enhanced_encryption

2. Secure Requests

Authorize your calls by injecting Authorization: Bearer <token> into the headers.

bug_report

Errors under the RFC 9457 standard

We return structured errors using the application/problem+json format, providing precise details to facilitate debugging.

400 Bad Request

{
  "type": "https://api.bridflow.com/problems/validation-error",
  "title": "One or more validation errors occurred.",
  "status": 400,
  "detail": "The request body failed validation.",
  "instance": "/transfers/auto/v1",
  "errors": {
    "destinationSavedContactId": [
      "The destinationSavedContactId field is required."
    ],
    "route": [
      "The route field is required."
    ]
  }
}