brapi vs Brazil CVM Filings API
brapi vs CVM filings API compares different products. brapi focuses on Brazilian market data (quotes and related endpoints). apicvm focuses on CVM regulatory filings over HTTP. Complementary — never "replace brapi".
Side-by-side
| Capability | brapi | apicvm |
|---|---|---|
| Quotes / market data | Core product | No |
| CVM DFP/ITR/FRE PDF by document ID | Not the product shape | Yes |
| Resolve by Brazilian ticker / CNPJ for filings | Not a filings API | Yes |
| Async page markdown extraction | No | Yes (Pro) |
Developer shape
import os, requests
BASE = os.environ["APICVM_URL"]
H = {"Authorization": f"Bearer {os.environ['APICVM_KEY']}"}
company = requests.get(
f"{BASE}/v1/companies/resolve",
headers=H,
params={"query": "PETR4", "by": "ticker"},
).json()Pair brapi (or any quotes API) with apicvm when models need the filing PDF. See Quotes APIs vs filings.
When apicvm is the better fit
- Regulatory document archives for Brazil
- Agent tools that must cite CVM document UUIDs
- FRE section retrieval
When brapi is the better fit
- Quote and market-data workloads for B3 symbols
- Apps that do not need PDF filings
- Teams without a regulatory archive requirement
Current limitations
- apicvm does not ship OHLCV endpoints
- We do not document brapi's entitlements or symbol coverage
- Filings availability follows ingestion, not tick prints
Next steps
Ready to integrate?
Get an API key and start querying Brazilian CVM filings programmatically.