What API2Cart Is Evaluating for Conta Azul Integration
Candidate data flow
Commerce sales connected with customers, products, invoices, and receivables. The final entity and method list will be based on verified vendor API capabilities rather than assumptions.
Operational outcome
The intended workflow is to preserve Brazilian tax and payment context without unsupported assumptions. Record ownership and idempotency would be defined before write operations are enabled.
Accounting safeguards
The connector would need to support clearer coordination between merchants and accountants. Orders, invoices, payments, refunds, settlements, and journal entries would not be treated as interchangeable records.
Develop Integrations Faster and Save Up to 9x on Costs
Trusted by
What We Know About Conta Azul So Far
Based on Conta Azul’s own documentation and API2Cart’s discovery process — not a promise of a release date.
API & Integration. Conta Azul exposes a REST API authenticated via OAuth 2.0 authorization-code flow, with client ID/secret issued through its developer portal and access scoped per connected client. It enforces published rate limits (on the order of ~50 requests/minute, up to 10/second, returning 429 on excess) and currently has no webhook support, so integrations must poll for changes. There is no persistent sandbox; instead, developers get a time-limited (30-day, renewable) developer account populated with fictional data for testing.
Is this integration live yet? No. Conta Azul integration is not live yet. Authentication, entities, fields, write operations, webhooks, limits, regional availability, and release timing remain subject to technical discovery and customer demand.
What’s the integration challenge? Engineering discovery must validate OAuth access, partner eligibility, fiscal-document boundaries, and webhook behavior. Unsupported objects or operations would remain outside the published scope.
How is a release decided? Roadmap evaluation includes API maturity, sandbox access, accounting correctness, customer demand, maintenance cost, data residency, rate limits, and overlap with existing connectors. The page records an integration candidate; it does not promise a release date.
Technical validation. Engineering discovery must validate OAuth access, partner eligibility, fiscal-document boundaries, and webhook behavior. Unsupported objects or operations would remain outside the published scope.
Primary sources: Conta Azul official website · Official developer or product documentation
Related planned integrations: Xero integration · Wave Accounting integration · Zoho Books integration · Sage Intacct integration
Interested in Conta Azul Integration?
Let us know you’re interested, and we’ll notify you as soon as Conta Azul support becomes available.
