Infrastructure to build on
Not a platform to use. It's infrastructure to build on. Connect your application to the BLOCKBR API and operate digital assets with brand, journey, and front-end under your control.
The visible layer is yours. The operational layer is ours.
Filter · Who it's for
BLOCKBR Connect API is modular infrastructure to build on — not a ready-made platform. Before continuing, see if your scenario calls for this path.
You have an in-house tech team or hire dedicated front-end development resources.
You want brand, journey, and end customer under your control. Invisible vendor.
You're launching more than one product — scale on the same foundation.
Endpoints, webhooks, and SDKs are familiar vocabulary for your team.
You build the application. The foundation is ours.
You want a ready-made platform — login, screens, visual flows already done. Zero code.
You don't have a tech team. No dev, no way to consume the API. Non-negotiable.
You need just one operation. Not worth the effort.
You want to launch in days. Here the path is deeper.
Another BLOCKBR product fits better: EAI or Whitelabel.
Comparison · Three models
There are three paths to operate digital assets. Each solves a different problem — and has a different cost. Seeing them side by side avoids buying the wrong one.
Vendor screen. Vendor brand.
You want to operate tomorrow and the end-customer relationship can go through the platform.
Same platform. Logo swapped.
You need brand up front but won't build your own digital product.
You design. We deliver the infra.
You want total control over brand, journey, and product — and will scale more than one operation.
Documentation · The stack
The API is organized into six independent modules — each exposes its own endpoints. You integrate only what makes sense for your operation. No bundled licenses. No mandatory modules.
{ "document": { "type": "cpf", "value": "123.456.789-00" }, "profile": { "name": "Ana Souza", "email": "ana@dominio.com", "phone": "+5511999999999" }, "suitability": { "profile": "qualified", "completed_at": "2026-04-27" }, "webhook_url": "https://app.cliente.com/hooks" }
{ "investor_id": "inv_8h3K2xQ", "status": "pending_kyc", "kyc": { "step": "document_upload", "required": true }, "created_at": "2026-04-27T14:32:08Z" }
Each module delivers endpoint, schema, and webhook. Full documentation after technical signup.
Access docs →How to integrate · Developer journey
From the first call to the first operation in production. Each stage has clear deliverables and defined technical milestones. No "everything in days" promise — a real path.
Discovery and contracting
API keys.Integration and validation
/investors, /assets, /offerings, /wallets per scope.Go-live and operations
API keys.FAQ · Technical questions
REST over HTTPS. Request and response in JSON. Asynchronous events via event-driven webhooks — you register the URL and receive the payload when the event fires.
No GraphQL, no SOAP, no proprietary formats. Familiar standard for any tech team.
API keys + OAuth 2.0 depending on the module. Separate keys for sandbox and production. Scheduled rotation, immediate revocation via admin dashboard.
Webhooks are signed via HMAC — you validate the origin before processing the payload.
Yes, fully isolated. Sandbox has synthetic data, the same endpoints as production, but with no effect on real operations.
Released at Stage 01 of technical onboarding — your team can start integrating before the final commercial signature, within the proof-of-concept scope.
SLAs defined in contract — uptime, API response time, technical support turnaround. They vary by commercial tier and operation scope.
Public status page shows availability history. No mystery, no workarounds.
The model is Setup + Monthly retainer — calibrated by operation scope.
Values presented in a commercial proposal after the initial technical discovery. Transparent and predictable model.
Three steps: technical conversation with BLOCKBR engineering, scope discovery, commercial proposal.
Once the contract is approved, your application is registered and sandbox API keys are released. From there your team can integrate — with active technical support throughout the journey.
Connect your application
Talk to the BLOCKBR technical team. In an initial conversation you define which modules to consume, the integration scope, and the path to production. Technical setup and proposal presented after discovery.