Brigit API integration & OpenBanking data export

1. Linked-bank transaction export

Because Brigit requires a Plaid bank link to work, the account behind it holds the richest consumer-permissioned data in the app: multi-account balances, 24+ months of transaction history, recurring deposit detection, and merchant-level categorization. Our integration exposes this as GET /brigit/bank/transactions with account_id, from, to, cursor paging and ISO-4217 currency, so you can sync it into QuickBooks, Xero, data warehouses, or underwriting models.

2. Instant Cash advance ledger

The Instant Cash product issues $25–$500 advances with no interest, no tips, no late fees, and a user-set repayment date. We expose the full ledger — disbursal channel (ACH vs debit-card express), amount, scheduled repayment, actual settlement, optional express fee, and the eligibility signal used to gate approvals — so risk teams can model repeat-borrower cohorts or white-label the flow.

3. Credit Builder installment API

Credit Builder opens a 24-month installment loan issued by Coastal Community Bank (Member FDIC). Monthly payments ($1–$25) are reported to all three US credit bureaus. Our endpoint GET /brigit/credit-builder/schedule returns the amortization plan, on-time flags, next reporting date, and the secured balance that gets returned to the user at payoff — ideal for credit-health dashboards.

4. Budgeting & subscription insights

Brigit's budgeting tools classify income, spend categories and active subscriptions (to help users cancel what they don't use). We surface those derived signals via GET /brigit/insights/subscriptions and GET /brigit/insights/cashflow, useful for budgeting copilots, B2B wellness dashboards, and employer financial-health programs.

5. Identity & alerts channel

Brigit Plus includes up to $1M identity-theft protection and real-time bank-balance alerts. We expose alert webhooks (low balance, unusual debit, credit-score change) so partners can embed overdraft-avoidance and identity signals into their own apps, including push bridges to Slack, email or SMS gateways.

6. Marketplace & offers feed

In 2024 Brigit expanded its Marketplace — side-gig listings, play-to-earn games, cashback deals and personal-loan offers from third-party lenders. We provide a structured feed (offers[], gigs[], loan_offers[]) with CPA/affiliate metadata, which is valuable for cashback aggregators and income-augmentation platforms.

Scenario A — Cash-flow underwriting for a BNPL lender

A Buy-Now-Pay-Later provider wants to underwrite thin-file borrowers who already use Brigit. We pull the consumer-permissioned linked-bank transaction stream plus Credit Builder on-time flags, score pay-cycle stability, and expose /underwrite/cashflow-score. This combines OpenBanking transaction data with behavioral repayment history — richer than a bare FICO file and fully Section 1033 compliant.

Scenario B — Personal-finance copilot / budgeting app

A budgeting copilot wants to import a user's Brigit-detected subscriptions and spend categories, then offer one-tap cancellation and savings goals. Our integration maps Brigit's subscriptions[] and cashflow.categories[] into a neutral schema, letting the copilot show "Cancel Hulu, save $17.99/mo" style nudges without re-linking every bank account.

Scenario C — Employer financial wellness dashboard

An HR-tech platform embeds Brigit's Credit Builder status and overdraft-alert counts (consented) into an employee financial wellness score. Our webhook stream pushes credit_builder.payment_on_time and balance.low_alert events; HR teams then surface anonymized cohort trends without ever seeing raw transaction lines.

Scenario D — Loan-offer marketplace aggregation

A loan-comparison site wants to ingest the Brigit personal-loan panel (lender, APR range, max amount, expiration) alongside other cash-advance alternatives. We expose /brigit/offers/loans so the marketplace can rank and deduplicate offers across apps like MoneyLion Instacash, Dave ExtraCash and Empower.

Scenario E — Compliance & audit export

A state-regulated lender needs an auditable export of every Brigit cash-advance interaction for a specific user (disclosure page shown, repayment date chosen, express fee paid). We package a signed JSON + PDF bundle from /brigit/audit/bundle, satisfying CFPB and state-AG discovery requests.

Deliverables checklist

• OpenAPI 3.1 specification (Swagger UI bundled)
• Protocol & auth flow report (mobile handshake, token refresh, device binding)
• Reference source: Python + Node.js clients, Dockerized gateway
• Postman collection with seeded sandbox responses
• End-to-end test suite (pytest + GitHub Actions)
• Compliance memo: CFPB §1033, GLBA, FCRA, state cash-advance rules
• 30-day post-delivery support, named engineer

API example 1 — Session bind & OAuth-style token

POST /api/v1/brigit/session/bind
Content-Type: application/json

{
  "device_id": "ios-8E3F...",
  "user_ref": "partner_user_42",
  "consent_token": "cfpb1033_permission_xyz"
}

// 200 OK
{
  "access_token": "brg_at_live_f7c9...",
  "refresh_token": "brg_rt_live_b201...",
  "expires_in": 1800,
  "scopes": ["bank.read","advance.read","builder.read"]
}

API example 2 — Linked-bank transaction statement

GET /api/v1/brigit/bank/transactions
?account_id=plaid_acc_0x91&from=2026-01-01&to=2026-03-31&cursor=

Authorization: Bearer <ACCESS_TOKEN>

// 200 OK
{
  "account_id": "plaid_acc_0x91",
  "currency": "USD",
  "next_cursor": "eyJwYWdlIjoyfQ==",
  "items": [
    {
      "id": "txn_9f21",
      "posted_at": "2026-03-12T14:22:00Z",
      "amount": -17.99,
      "merchant": "HULU",
      "mcc": "4899",
      "category": "subscription.streaming",
      "is_recurring": true
    }
  ]
}

API example 3 — Credit Builder event webhook

POST https://partner.example.com/hooks/brigit
X-Brigit-Signature: t=1714000000,v1=9a4d...

{
  "event": "credit_builder.payment_reported",
  "occurred_at": "2026-04-01T09:00:00Z",
  "user_ref": "partner_user_42",
  "data": {
    "payment_amount": 10.00,
    "on_time": true,
    "bureaus": ["experian","equifax","transunion"],
    "months_remaining": 17,
    "issuer": "Coastal Community Bank"
  }
}

// Error handling: non-2xx responses are retried
// with exponential backoff (max 24h).

About the studio

We are an independent technical studio focused on app interface integration and authorized API work for global clients. Our team combines engineers with hands-on experience across US fintech (Plaid, Dwolla, Stripe Treasury), mobile reverse engineering on iOS/Android, and cloud-native API delivery. For cash-advance and credit-building apps like Brigit we own the full pipeline: protocol analysis of the mobile client, reconstruction of the OAuth/token flow, Section 1033-aligned consent plumbing, endpoint hardening, and full test/ops documentation.

• US fintech, OpenBanking and consumer-credit integrations
• Protocol analysis, SDK rebuild, gateway deployment
• Python, Node.js and Go client libraries
• Source code delivery from $300 — runnable code, docs and tests; pay after delivery once you're satisfied
• Pay-per-call hosted API — no upfront fee, usage-based pricing for teams that want to ship quickly

Contact

Send us the target app (Brigit: Cash Advance & Credit), the data you need (e.g. transaction export, Credit Builder events), and any sandbox credentials you already have. We'll return a scoped quote within one business day.

Open contact page

Two engagement models: source-code delivery from $300, or pay-per-call API with no upfront cost.

Engagement workflow

1. Scope confirmation — which Brigit surfaces you need (transactions, advance ledger, Credit Builder, alerts).
2. Protocol analysis & API design (2–5 business days).
3. Implementation & internal validation (3–8 business days).
4. Docs, Postman samples, test cases, compliance memo (1–2 business days).
5. Typical first delivery: 5–15 business days; complex Section 1033 or state-by-state gating may extend timelines.

FAQ

What do you need from me?

Is this compliant under US rules?

Can you cover Dave, EarnIn or MoneyLion too?

How is pricing structured?