Getting structured data out of a Bamaq consortium quota

Every Bamaq consortium quota carries a running ledger: paid installments, the next boleto with its due date, the bid history for the group, and where the quota stands in the monthly assembly. The Bamaq Consórcio client app — package org.orbbits.bmqcliente per its Play Store listing — is where a consorciado reads all of that. None of it leaves the app on its own. Getting it into an accounting system, a treasury dashboard, or a CRM means reading the same authenticated portal the app reads, and that is the work described here.

The practical path for this app is to operate a single consenting quota and read its portal traffic directly — that reaches the extrato, the boletos and the lances in one pass, which is where almost every integration request for a consórcio app actually lands. Open Finance Brasil sits alongside it for anything that touches the customer's bank account, not the consortium ledger. The rest of this page maps the data, the routes, and what we hand over.

What a consortium quota holds

These are the surfaces the app exposes to a logged-in consorciado, named the way Bamaq names them. Granularity below is what the screens imply; exact field names are confirmed against a live account during the build.

Routes into the quota data

Two or three approaches fit a consórcio app like this one. They are not mutually exclusive; most builds combine the first two.

Authorized interface integration on a consented account

We operate a quota the client controls and read the portal's own client-server traffic — the same calls the app makes for extrato, boletos, lances and assemblies. Reach is the whole authenticated area. Effort is moderate. Durability is tied to the portal front end, so it carries a maintenance commitment. Onboarding sets up the consenting account and a replay harness against it; that is our step, arranged with you, not something you hand over finished.

User-consented credential access

Where the client wants their own login driven rather than a fresh test quota, we operate it under a written consent record, scoped to that account. Reach is identical; durability is steadier because nothing depends on a sandbox staying alive. Credential handling stays vaulted and logged.

Open Finance Brasil, for the bank edges

The consortium quota itself is not a standard Open Finance data category. What Open Finance does cover — the consorciado's bank account, the debit that funds a boleto — is reachable through the regulated consent flow when that side of the picture matters. We wire it in only where it earns its place; it does not replace reading the Bamaq portal.

For most teams the first route, run on a consenting account, carries the integration on its own — it is the only one that returns the full extrato, the live boletos and the bid history together. We layer the bank-side Open Finance flow on top when reconciliation against the funding account is in scope, and keep credential access as the option when the client would rather we drive their existing login than stand up a test quota.

A statement pull, sketched

Illustrative shape, not a promised contract — host, paths and field names are confirmed against a live quota during the build. Auth here is the app's own session token; the full token and refresh chain goes in the auth-flow report.

import requests

BASE = "https://app.bamaqconsorcio.com.br"        # client portal host (illustrative)

def login(cpf, senha):
    r = requests.post(f"{BASE}/auth/login",
                      json={"cpf": cpf, "senha": senha})
    r.raise_for_status()
    return r.json()["accessToken"]                  # bearer for later calls

def extrato_cota(token, grupo, cota):
    r = requests.get(f"{BASE}/cotas/{grupo}-{cota}/extrato",
                     headers={"Authorization": f"Bearer {token}"})
    if r.status_code == 401:
        raise SessionExpired("re-auth before retry")  # handled by the refresh wrapper
    r.raise_for_status()
    p = r.json()
    return [
        {"parcela":    l["numero"],
         "vencimento": l["vencimento"],
         "valor":      l["valor"],
         "pago":       l["situacao"] == "PAGO"}
        for l in p["parcelas"]
    ]

# A second call against /cotas/{id}/boletos returns the open slip
# and its linha digitável for the next due installment.

What lands in your repository

The deliverable is working code plus the documents that let your team own it, all keyed to the surfaces above:

• An OpenAPI/Swagger spec covering the quota endpoints — extrato, boletos, histórico, lances, assembleias.
• A protocol and auth-flow report: how login, the bearer token and its refresh behave, and how the portal frames each response.
• Runnable source for the key endpoints in Python or Node.js, structured so a statement pull and a boleto fetch are one function call each.
• Automated tests that run against a consenting quota, asserting field shapes so a silent change is caught early.
• Interface documentation a developer who never saw the app can follow.
• Data-retention and consent guidance written to LGPD — what to store, for how long, and how a revocation propagates.

Where teams plug Bamaq data in

• A dealer or fleet operator with dozens of quotas reconciling monthly contributions into its accounting system without anyone re-keying boletos.
• A treasury desk pulling open boletos and due dates nightly to forecast outgoings.
• An arrears workflow that watches the payment history and opens a case when an installment slips past its vencimento.
• A bid-strategy view that reads the group's lance history and flags when an assembly looks winnable.
• A CRM that fires a contemplation event the moment a quota is awarded, so the sales team reaches the client first.

What we account for on the Bamaq side

A consórcio app has quirks a generic export script would miss. These are things we handle inside the build, not boxes you tick before we start.

• Plan-type divergence. Moto, carro, imóvel, máquina, caminhão and premium quotas follow different bid and eligibility rules. We map each grupo's plan so two quotas under one login are read and labelled correctly rather than flattened together.
• Assembly cadence. Contemplation, draw results and bid windows move on a monthly assembly clock. We pace the sync around that calendar instead of polling continuously, so the integration stays quiet between assemblies and busy when results land.
• Front-end drift. When Bamaq ships a new app build, response fields can move. A contract-check job compares live responses against the agreed schema and raises a flag before a changed field reaches your pipeline.
• Session lifetime. The portal token expires; the sync is built around its refresh window so a long-running job does not die mid-pull. Access to a consenting quota is arranged with you during onboarding — the build runs against that account or a sandbox the project sets up together.

Consent, the Central Bank, and LGPD

Consórcio in Brazil is supervised by the Banco Central do Brasil under Lei nº 11.795/2008, which since February 2009 has set who may run an administradora and how quotas are governed; the sector body ABAC publishes guidance alongside it. None of that is an interface to the data, so the dependable basis for our work is the consorciado's own authorization to read their quota. Consent is recorded electronically — free, informed and specific, as LGPD (Lei 13.709/2018, overseen by the ANPD) requires — and it is revocable; when a client withdraws it, the integration stops reading and the retention guidance says what gets purged. We minimise to the fields the use case needs, log every access, and sign an NDA where the engagement calls for one. Open Finance Brasil is the country's regulated data-sharing rail for bank, insurance and investment data; we use its consent flow for the bank-side legs and keep the quota reads on the authorized-interface path.

Cost and cadence

Source for the extrato and boleto endpoints reaches your repository inside one to two weeks of a green build against a consenting quota. Take it as delivered code — runnable API source, the auth-flow report, and tests — from $300, invoiced only after it is in your hands and working as agreed. Or skip running anything yourself and call our hosted endpoints, paying per call with nothing upfront. Either way the cycle is one to two weeks. Send the app name and what you need from the quota data to /contact.html and we scope it back to you.

From the app screens

Store screenshots of the Bamaq Consórcio client app — the surfaces the data is read from. Tap to enlarge.

Other consórcio apps in the same shape

Brazil's consórcio market runs through a handful of administradoras, each with its own client app over a similar quota ledger. A team integrating Bamaq usually wants one or two of these normalised to the same schema.

• Embracon — large independent administrator; its client app exposes quota statements, boletos and assembly results in much the same shape.
• Rodobens Consórcio — decades-old auto and real-estate administrator; quota tracking, bids and payment slips in its app.
• Ademicon — one of the largest independents, Curitiba-based; real-estate, vehicle and service quotas with statement and bid screens.
• Porto Consórcio — the consórcio arm of Porto Seguro; quota data sits inside a broader insurance and banking app.
• Magalu Consórcio — retail-linked administrator; quota balances and boletos surfaced through the group's app.
• HS Consórcios — vehicle-focused administrator with a client area for statements, bids and contemplation status.
• Servopa Consórcio — long-running southern administrator; quota statement and payment management in its app.
• Bancorbrás — consórcio and benefits group; quota and payment data behind a member login.

How this brief was checked

Compiled on 11 June 2026 from the app's store listings and Bamaq's own client-app and help pages for the named surfaces (extrato, boletos, lances, assemblies, anticipation and renegotiation), and from primary regulatory sources for the supervisory and open-data context. Sources opened: the Google Play listing; Bamaq's help centre on bids and draws; the text of Lei nº 11.795/2008; and Open Finance Brasil.

OpenBanking Studio integration desk · mapping reviewed 11 June 2026.

Questions integrators ask about Bamaq

Can two quotas under one Bamaq login be read separately?

Yes. A single client can hold several cotas across different grupos and plan types, so the integration is scoped per grupo-cota pair rather than per login. Each quota's statement, boletos and bid history are pulled and labelled independently.

Does the quota statement arrive through Open Finance Brasil?

Open Finance Brasil standardises banking, insurance and investment data, not the consórcio quota ledger, which sits in Bamaq's own client portal. We read the extrato, boletos and lances through authorized interface integration on a consenting account, and use Open Finance only for the bank-side payment flows where it applies.

What happens to the integration when Bamaq ships a new app build?

Response shapes can shift when the portal front end changes. We keep a contract-check job that compares live responses against the agreed schema and flags any changed or dropped field before it reaches your pipeline, so a Bamaq release does not quietly break the sync.

If we only need boletos and payment history, can we run something smaller?

Yes. A narrow scope — say second-copy boletos and the histórico de pagamentos for reconciliation — maps cleanly to the pay-per-call hosted endpoints, so you pay only for the calls you make instead of commissioning the full quota integration.