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 virtual account in 3 steps

Our API is built for the best Developer Experience. Go from zero to production in record time.

index.js

Live API Playground

Try the API without signing up

Generate real requests to our Sandbox environment directly from the browser and see the response speed.

tune Configure Request

Endpoint

POST POST /v1/virtual-accounts

Fiat Currency

Blockchain Network

Settlement Token

Response

terminal Click "Execute Request" to test the API.

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 GET "https://api.bridflow.com/v1/ping" \
  -H "Authorization: Bearer YOUR_API_KEY"

// Response defined by OpenAPI

{
  "status": "success",
  "message": "API is operational",
  "version": "1.0.0"
}

Ready to integrate? Discover BridflowDocs 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

Server-to-Server & OAuth 2.0

Our API uses an OAuth 2.0 Client Credentials Grant flow. All requests must originate from your backend (Server-to-Server) to protect your API Keys.

lock_open

1. Token Generation

POST /oauth/token returns a short-lived JWT (1 hour).

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/errors/insufficient-funds",
  "title": "Insufficient Funds",
  "status": 400,
  "detail": "El balance actual es inferior al coste de la operación.",
  "instance": "/v1/transfers/req_123xyz",
  "balance": "150.00",
  "currency": "EUR"
}