Coinext: Comprar Bitcoin — API integration & OpenFinance data services

1. Authenticated account access

Coinext exposes username + password basic authentication and granular API keys with read-only, trading, transfer and IP-restriction scopes. We wrap both flows into a single SDK call (client.login()) and manage token refresh, HMAC signing and session expiration so your service never ships plaintext credentials.

Concrete use: multi-tenant SaaS tools that onboard Brazilian traders can bind a read-only key to each customer and start pulling balances within minutes.

2. Pix deposit & withdrawal telemetry

The Coinext Pix rail confirms deposits in ~2 minutes and withdrawals in ~3 minutes using the identifier pix@coinext.com.br, QR codes or registered Pix keys. Our connector surfaces each Pix event (status, end-to-end ID, counterparty, amount, fee) as a webhook suitable for downstream treasury or ERP automation.

Concrete use: corporate accounts reconciling daily BRL inflows against invoice IDs or driver settlements.

3. Transaction history & statement API

Exposes executed orders (Market, Limit, Stop-Limit) across all 60+ pairs with paging, date filters and side (buy/sell). Fields include order_id, pair, price, base_qty, fee_brl, created_at. Output formats: JSON, CSV, XLSX and signed PDF statements for tax filings.

Concrete use: accounting platforms building cost-basis calculations for Brazilian crypto declarations.

4. Smart Wallet & automated trading

Coinext's Smart Wallets execute AI-driven trades starting from R$200, with backtested performance tracked by Qinv Con. Our API exposes current allocation, historical NAV, weekly yield and individual rebalance transactions for dashboard or compliance use.

Concrete use: wealth dashboards combining Smart Wallet positions with off-exchange assets into a single performance view.

5. Market data, WebSocket order book

Public services such as GetL2Snapshot, ticker and trades streams are mirrored through a normalized WebSocket gateway. We deliver typed message handlers (TypeScript / Python) with automatic reconnect, heartbeat and L2 rebuild logic.

Concrete use: quant shops that need clean Brazilian-pair liquidity feeds next to global venue data.

6. Alternative-asset tokens

Coinext lists tokenized music royalties, precatórios (court-ordered payments) and artworks. The integration exposes token metadata, issuer, distribution schedule and user holdings so wealth advisors can aggregate non-crypto exposure in the same reports.

Concrete use: family-office reporting tools unifying digital assets with alt-asset tokens under one ledger.

A. Accounting & tax reporting sync

Business context: a Brazilian accounting SaaS (for example, serving CNPJ holders that declare crypto on IN 1888 / DeCripto) needs monthly statements.

Data / API: Coinext statement API (/v1/statement), Pix webhook, fee records. Fields: pair, side, price_brl, fee_brl, settlement_date.

OpenData mapping: mirrors OpenFinance "transactions and balances" primitives; payload shape aligned with BCB Phase 2 data sharing contracts for non-bank institutions.

B. Corporate treasury reconciliation

Business context: a Brazilian PSP receives client payments in BRL via Pix and hedges into USDT on Coinext.

Data / API: Pix deposit webhook → Smart Wallet / Limit order execution → BRL / USDT balance snapshot. Fields: endToEndId, order_id, executed_qty, cost_brl.

OpenData mapping: cash-flow telemetry feeds directly into OpenBanking treasury dashboards and ERP.

C. Portfolio & wealth advisory

Business context: a wealth advisor aggregates Coinext Smart Wallet and alt-asset token holdings with stocks held at brokerage.

Data / API: GetUserInfo, Smart Wallet NAV endpoint, alt-asset token balance. Fields: strategy_id, nav, weekly_yield, token_id.

OpenData mapping: matches OpenFinance Phase 3 "investment products" sharing — unified view across crypto, tokenized royalties and traditional investments.

D. Compliance & Travel Rule

Business context: a VASP partner needs originator/beneficiary information on transfers over R$10,000 per CVM / BCB VASP rules.

Data / API: On-chain transfer log, KYC tier, Pix counterparty. Fields: txid, amount_brl, counterparty_vasp, cpf_hash.

OpenData mapping: ties into VASP registry feeds that the Brazilian Central Bank is finalizing in its 2024–2025 VASP authorization framework.

E. Market analytics & quant backtests

Business context: a research desk backtests BRL arbitrage between Coinext and global venues.

Data / API: GetL2Snapshot, trades WebSocket, historical OHLCV dump. Fields: bid/ask levels, trade_id, price, qty, timestamp.

OpenData mapping: normalized market-data schema compatible with FIX and OpenFinance real-time quote extensions.

Deliverables checklist

• OpenAPI 3.1 specification for every endpoint we ship
• Protocol & authentication report (basic auth, API key HMAC, session lifecycle)
• Runnable source in Python / Node.js / Go with unit and contract tests
• Postman collection + cURL examples for QA teams
• Compliance dossier (KYC fields, data retention, Brazilian LGPD alignment)
• Deployment notes for AWS / GCP / self-hosted Docker

Snippet 1 — Authenticated statement query

POST /api/v1/coinext/statement
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json

{
  "account_ref": "user_9f31",
  "from_date":   "2026-01-01",
  "to_date":     "2026-01-31",
  "assets":      ["BTC","ETH","USDT"],
  "order_types": ["Market","Limit","Stop"]
}

// 200 OK
{
  "page": 1,
  "items": [
    {"order_id":"c9a8","pair":"BTC/BRL","side":"buy",
     "price_brl":345120.11,"qty":0.0134,"fee_brl":5.78,
     "executed_at":"2026-01-07T14:02:11Z"}
  ],
  "next_cursor": "c9b0"
}

Snippet 2 — Pix deposit webhook

POST https://your-service.example.com/hooks/coinext-pix
X-Coinext-Signature: t=1738000000,v1=5f2e...

{
  "event": "pix.deposit.confirmed",
  "end_to_end_id": "E2025100712001234567",
  "account_ref": "user_9f31",
  "amount_brl":  1500.00,
  "fee_brl":     0.00,
  "payer":       { "name": "***", "cpf_hash": "7f1c..." },
  "received_at": "2026-01-07T14:00:58Z"
}

// verify HMAC with shared secret
// then credit internal ledger idempotently by end_to_end_id

Snippet 3 — Market data WebSocket

// TypeScript — normalized feed
const ws = new CoinextFeed({ apiKey, scope: "md" });

ws.subscribe("BTC/BRL", { depth: 25 });
ws.on("l2snapshot", (msg) => updateBook(msg.bids, msg.asks));
ws.on("trade", (t) => ingest({
  pair: t.pair,
  price: t.price_brl,
  qty: t.qty,
  taker: t.taker_side,
  ts: t.ts_ms,
}));

ws.on("error", (e) => logger.warn("reconnect", e));
// auto-reconnect with jittered backoff, heartbeat 15s

Compliance & privacy

Coinext operates under Brazilian law, and all integrations we build respect the current VASP (Virtual Asset Service Provider) framework published by the Banco Central do Brasil (BCB) and coordinated with the CVM, together with the LGPD (Lei Geral de Proteção de Dados, Law 13.709/2018) for personal-data handling. Where applicable, OpenFinance integrations follow BCB Joint Resolution 10/24 and Resolution 400/2024 (effective January 2, 2025), which expanded mandatory participation and introduced Pix-by-approximation and single-use consent mechanisms.

Concretely this means: every connector ships with explicit consent logs, purpose-of-use metadata, data-minimization filters (CPF hashing, opt-in for enrichment fields) and configurable retention windows. We reject integrations that would require unauthorized scraping of user-facing screens; all flows use documented API keys or customer-authorized tokens.

Data flow / architecture

A reference Coinext integration typically follows a four-node pipeline. Each node is observable and fails safely:

Events flow from the Coinext HTTP / WebSocket surface into an ingestion gateway that validates signatures and enforces rate limits. Normalized records land in a relational store for warm queries and an object store for statement exports. Downstream consumers reach a single OpenFinance-style API that speaks JSON / CSV / Parquet.

About our studio

We are an independent studio focused on fintech protocol analysis and authorized OpenData / OpenFinance / OpenBanking API integration. Our engineers come from Brazilian banks, payment gateways, crypto exchanges and cloud security teams, and have shipped integrations against Pix, SPI, UPI, PSD2 and Open Banking UK contracts.

• Payments, digital banking, crypto and cross-border clearing
• Enterprise API gateways, HMAC signing, mTLS and security reviews
• Python / Node.js / Go / TypeScript SDKs with CI-tested release pipelines
• Full pipeline: protocol analysis → design → build → validation → compliance dossier
• Source code delivery from $300 — runnable API source code and full documentation; pay after delivery upon satisfaction.
• Pay-per-call API billing — access our hosted Coinext-compatible endpoints and pay only per call, no upfront fee.

Contact

Share your target app name (Coinext: Comprar Bitcoin) and the exact data scope you need — statements, Pix reconciliation, Smart Wallet positions, market data, or a custom bundle. We'll scope timeline, price and compliance review within one business day.

Open contact page

Preferred engagement: NDA-first; scoped deliverables; milestone-based payments. Pay-per-call available for teams that want to avoid upfront spend.

Engagement workflow

1. Scope confirmation: list the Coinext data surfaces (login, statements, Pix, Smart Wallet, market data) and target deployment.
2. Protocol analysis and API design — 2–5 business days (complexity dependent).
3. Build and internal validation against Coinext sandbox / live account — 3–8 business days.
4. Documentation, Postman collection and contract tests — 1–2 business days.
5. Typical first delivery: 5–15 business days. Additional CVM/BCB or customer-side approvals may extend timelines.

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?

Do you support pay-per-call?