Poli API Integration & Open Finance Data Solutions

Authentication & Session Bootstrap

// Step 1: User account login (pseudocode)
POST /api/v1/poli/auth/login
Content-Type: application/json

{
  "credential": "<user_identifier>",
  "device_token": "<device_fingerprint>",
  "consent_scope": [
    "transactions",
    "investments",
    "reports"
  ]
}

// Response 200 OK
{
  "access_token": "eyJhbGci...",
  "refresh_token": "dGhpcyBp...",
  "expires_in": 3600,
  "scope": ["transactions","investments","reports"],
  "consent_id": "cns_8f3a9d2b"
}

// Step 2: Refresh before expiry
POST /api/v1/poli/auth/refresh
Authorization: Bearer <REFRESH_TOKEN>
→ Returns new access_token + expiry

Transaction History Query

// Fetch paginated expense/income transactions
GET /api/v1/poli/transactions
Authorization: Bearer <ACCESS_TOKEN>

Query params:
  from_date=2025-01-01
  to_date=2025-03-31
  type=expense         // expense | income | all
  category=food        // optional
  page=1&per_page=50

// Response 200 OK
{
  "total": 142,
  "page": 1,
  "items": [
    {
      "id": "txn_4a2f1c",
      "date": "2025-03-15",
      "amount": -89.50,
      "currency": "BRL",
      "category": "food",
      "description": "Supermercado Pão de Açúcar",
      "type": "expense"
    }
  ]
}

// Error codes:
// 401 → token expired → call /auth/refresh
// 429 → rate limited → retry after header

Investment Portfolio Snapshot

// Retrieve investment positions
GET /api/v1/poli/investments/portfolio
Authorization: Bearer <ACCESS_TOKEN>

// Response 200 OK
{
  "total_invested": 45000.00,
  "currency": "BRL",
  "last_updated": "2025-04-01T09:00:00Z",
  "positions": [
    {
      "asset_id": "inv_b3_cdb01",
      "type": "fixed_income",
      "name": "CDB 110% CDI",
      "current_value": 12300.00,
      "performance_pct": 8.4,
      "allocation_pct": 27.3
    },
    {
      "asset_id": "inv_fii_hglg11",
      "type": "real_estate_fund",
      "name": "HGLG11",
      "current_value": 8750.00,
      "performance_pct": 5.1,
      "allocation_pct": 19.4
    }
  ]
}

Webhook Subscription for Real-Time Events

// Register webhook endpoint
POST /api/v1/poli/webhooks/subscribe
Authorization: Bearer <ACCESS_TOKEN>

{
  "url": "https://your-service.com/hooks/poli",
  "events": [
    "transaction.created",
    "budget.exceeded",
    "investment.updated"
  ],
  "secret": "<HMAC_SECRET>"
}

// Response 201 Created
{ "webhook_id": "wh_7c3d9a", "status": "active" }

// Incoming event payload (POST to your URL)
{
  "event": "transaction.created",
  "timestamp": "2025-04-10T14:32:11Z",
  "data": {
    "txn_id": "txn_9f2e1a",
    "amount": -45.00,
    "category": "transport",
    "type": "expense"
  },
  "signature": "sha256=abc123..."
}
// Verify: HMAC-SHA256(payload, secret) === signature

Open Finance Brasil — BCB Resolution 1/2020

Brazil's Open Finance system, established by the Banco Central do Brasil under Resolution 1/2020, requires participating institutions to expose standardized APIs for data sharing and payment initiation, gated by explicit user consent. By January 2025 the ecosystem counted 62 million active consents, recorded over 102 billion API calls throughout 2024, and a new governance body — the Open Finance Brasil Association — was established in 2024 to professionalize decision-making across 800+ participating institutions. Any Poli integration that feeds regulated downstream platforms must implement and honor the BCB's consent lifecycle management model, including consent creation, revocation endpoints, and purpose-limited data access scopes.

LGPD — Lei Geral de Proteção de Dados (Law 13,709/2018)

Brazil's General Data Protection Law (LGPD), modeled closely on Europe's GDPR, governs all processing of personal financial data. Every Poli integration our studio delivers includes: explicit user consent records per Article 7, data minimization (only fields required for the stated integration purpose are requested), right-to-erasure workflow documentation per Article 18, and a data-processing agreement template. Financial data fields are never retained beyond the purpose scope defined at consent time, and all access events are logged for auditability under Article 46 security obligations. We provide a compliance checklist with each source code delivery.

Mobills

One of Brazil's most-downloaded expense trackers, Mobills stores detailed credit card invoice records, recurring expense schedules, and category-level spending breakdowns. Teams building Open Finance aggregators that include both Poli and Mobills users frequently need a cross-app transaction deduplication layer to prevent double-counting when the same purchase is recorded in both apps.

Organizze

Organizze focuses on multi-bank account management, holding consolidated balance snapshots, income and expense records across multiple accounts, and monthly budget targets. Platforms building complete net worth views require both Organizze's multi-account balance data and Poli's investment position data — making a combined integration the most common enterprise request in this category.

GuiaBolso / PicPay

GuiaBolso pioneered automatic bank account linking via Open Finance in Brazil before being acquired by PicPay (2021) and merged into PicPay's super-app platform. Its legacy transaction feed architecture — real-time bank transaction ingestion with category auto-tagging — established the Brazilian market's expectation for financial data integration quality, serving as a direct reference benchmark for Poli-compatible aggregation pipelines.

Wallet by BudgetBakers

A globally available multi-currency expense tracker with bank connection capabilities across dozens of countries, Wallet holds cross-currency transaction records, balance data, and household shared ledgers. Users who hold Brazilian Real investments in Poli alongside international assets tracked in Wallet benefit from cross-platform normalization integrations that reconcile multi-currency positions into a single net worth calculation.

Spendee

Spendee offers shared wallet functionality and automatic multi-bank transaction imports with category intelligence. Its structured category hierarchy and household-level aggregation data complement Poli's individual investment tracking — making combined Spendee + Poli integrations valuable for family financial management products where one member tracks household spending in Spendee while monitoring personal investments in Poli.

Monarch Money

A US-based personal finance platform with investment tracking, net worth monitoring, and an AI-powered financial assistant (expanded significantly in 2024). International fintech products adapting Monarch's feature profile for the Brazilian market regularly require Poli-compatible connectors to replicate Monarch's investment and expense data model using locally available data sources governed by Open Finance Brasil.

YNAB (You Need A Budget)

YNAB's zero-based budgeting system is built around category envelope allocations and manual transaction assignment. Brazilian users who budget in YNAB while tracking investments in Poli frequently request an automated bridge that exports new Poli expense transactions into YNAB's import format nightly, keeping both systems synchronized without double data entry across the two apps.

Fina

Fina is a customizable personal finance platform recognized in 2025 reviews for its automatic bank syncing, AI-powered spend insights, and investment portfolio overlay features. Its emphasis on data portability and API-friendly design makes it a natural downstream consumer of Poli's expense and investment data outputs — particularly for teams building a multi-source financial aggregation layer where Fina serves as the front-end and Poli provides one data feed.

Deliverables Checklist

• API specification — OpenAPI / Swagger format covering all endpoints
• Protocol and auth flow report: token lifecycle, consent scope management, device fingerprinting
• Runnable source code — authentication, transaction history, investment portfolio, category export, and webhook modules (Python / Node.js)
• Automated test suite with mock server for local development and CI integration
• LGPD & Open Finance Brasil compliance guidance: consent record templates, data minimization checklist, data-processing agreement
• Full API documentation with request / response field definitions and error code reference

Engagement Models

About Our Studio

We are an independent technical service studio specializing in app interface integration and authorized API integration. Our team brings hands-on experience in mobile protocol analysis, Open Finance implementations, fintech backend architecture, and enterprise API gateway design — with particular depth in Brazil's BCB regulatory framework, Open Finance Brasil standards, and LGPD compliance requirements for financial data processing.

• Financial management, digital banking, and investment platforms
• Open Finance Brasil API implementation (Phase 1–3)
• Custom Python / Node.js / Go SDKs and automated test harnesses
• Full pipeline: protocol analysis → build → validation → compliance review
• Global client base; English and Portuguese engagement supported

Contact Us

To request a quote or submit requirements for Poli API integration or any similar personal finance app, visit our contact page. Typical response time is 1 business day.

Open Contact Page →

When contacting us, please include: the target app (Poli / net.poliapp), your integration scenario (transaction export, investment sync, category API, etc.), preferred delivery language (Python / Node.js), and any existing cloud or backend environment details.

Engagement Workflow

1. Scope confirmation — Define integration scenarios (transaction export, investment sync, webhooks, category data) and delivery format (Python / Node.js). Usually completed within 1 business day by email or call.
2. Protocol analysis & API design — 2–4 business days to map Poli's auth flows, data structures, and API surface. Outputs an API design document for client review before build starts.
3. Build & internal validation — 3–7 business days for core modules (auth, transactions, investments, webhooks) with full test coverage against live and mock environments.
4. Documentation & test cases — 1–2 business days: OpenAPI spec, sample request/response pairs, error code reference, and compliance checklist.
5. Delivery & revision — Client acceptance period with one included revision round. Typical total timeline: 7–14 business days from scope sign-off.

FAQ

What do you need from me to start?

How is data compliance handled?

Can you integrate Poli alongside other apps?