Read first:
../conectores.md(state map) andfichas.md(index of the datasheets).
What it is#
Reads a public time series from the Central Bank's Time Series Management System (Selic, IPCA, PTAX, CDI…) for a given period and loads it into the Bronze layer.
Supported ingestion modes:
- Nós buscamos — We fetch the data from your source.
What it's for#
Bring Banco Central (SGS) data into your datalake and make it available to the Bronze/Silver/Gold layers, BI models, and the natural language question wizard.
When to use / when not to use#
Use when you need to consolidate this source into the datalake on a scheduled basis, with isolation per workspace.
Remember that the first run with a real credential is followed by our team before the connector is fully released.
Plan and permissions#
- Plan: core product (connectors are included in all plans; the limit is the number of sources in the plan).
- Access: requires an active workspace — with subscription overdue, suspended or canceled, the run is blocked.
- Shutdown: ingestion runs can be temporarily turned off (maintenance or incident). When this happens, the UI indicates the resource is unavailable at the moment.
Prerequisites#
- No credential required: the data is public.
- The Central Bank's open data API is public. Provide the series code in SGS (e.g., 11 daily Selic, 433 monthly IPCA, 1 PTAX sell dollar) and the period in dd/MM/yyyy. Note: for daily series the Central Bank limits each query to 10 years — split larger periods into more than one source.
Credentials#
Authentication method: No credential — public data.
This connector does not require its own secrets (upload mode / no credential on the platform).
Secrets are never re-displayed and undergo redaction in all errors/logs (raw token, URL-encoded and in JSON).
Form fields#
| Field | Label | Type | Required | Note |
|---|---|---|---|---|
serie | Série code (SGS) | text | yes | default: 11; Series number in the SGS catalog. Ex.: 11 (daily Selic), 433 (monthly IPCA), 1 (PTAX sell dollar), 4389 (annualized CDI). |
dataInicial | Start date | text | yes | Format dd/MM/yyyy. Daily series: maximum 10 years up to the end date. |
dataFinal | End date | text | yes | Format dd/MM/yyyy. Can be a future date — the Central Bank returns up to the last published value. |
Step by step#
- In the menu Dados → Conexões, use Nova conexão.
- Choose Banco Central (SGS) in the catalog.
- Fill in the form fields (see the table above).
- Use Testar conexão. The result is shown broken down into Conectividade, Autenticação and Listagem/leitura — each with OK, Failed, Not applicable or Not tested. A capability with no test of its own for this connector shows as Not applicable, and Not applicable never counts as success.
- Use Salvar conexão. Saving does NOT start any ingestion.
- On the connection card, use Montar extração (or go to Orquestração → Pipelines and use Conectar fonte). The pipeline points to the saved connection — the credential is not copied.
- In the review, Publicar (agenda desligada) creates version 1 without executing anything. Then, Ativar agenda and Executar agora are separate actions.
Example — connection test#
Sample configuration (all values are fictitious; secrets appear masked):
# Exemplo sintético (valores fictícios — não são credenciais reais)
serie = 11
dataInicial = <dataInicial>
dataFinal = <dataFinal>Expected result#
The Testar conexão returns the list of discovered tables/resources. After the first load, rows appear in the Bronze layer of your workspace, ready for the pipeline.
Limits and costs#
- Pagination: hard ceiling per run (default 10,000 pages / 5,000,000 rows); anti-loop guard.
- SaaS load: default
batchSize5,000,maxRows200,000 per resource. - Estimated volume: ~0.01 GB/month (catalog estimate, not measurement).
- Cost: the extraction itself is not billed by the platform; the Bronze load consumes datalake processing (billable).
Security#
- Scope by workspace: each client reads and writes only in their own datalake (
<prefix>_bronze/_silver/_gold); there is never leakage between workspaces. - Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being stored. The external credential vault is optional and linked per connection; without it, the encrypted value is stored in the database. Changing the value here does NOT revoke the credential at the origin.
- Redaction: all errors/logs go through secret redaction (raw, URL-encoded and in JSON).
- Production doesn't fake: a path that would fall into a mock triggers the production guard (explicit failure instead of simulating success).
Common errors#
- Credential rejected (401/403) — the provider did not accept the credential: expired, revoked or lacking necessary permission. Reconnect the source (the source and history are preserved; do not recreate the source).
- Rate limit (429) — the provider asked to wait. The extraction respects
Retry-Afterand retries; if repeated, wait and reduce the schedule frequency. - Resource not found — check the resource identifier (account, object, report) and the granted permissions.
- Pagination cursor stuck — the extraction stops when the API cursor does not advance (anti-loop guard). If it happens in successive runs, open a support ticket indicating the connector and the resource.
- Empty records path — the response arrived without records in the expected place. Check the selected resource and filters (period, account, status) before assuming there is no data.
Troubleshooting#
- Use Testar conexão to isolate credential/network issues before scheduling.
- Monitor runs in the connector observability (error rate, p50/p95, freshness).
- A schema change at the origin is flagged by the schema drift (new column = info; removed column/type changed = attention).
Related#
../conectores.md— connector catalog by state../ingestao-incremental-backfill.md— full, incremental by watermark, backfill and checkpoint../pipeline-medalhao.md— Bronze/Silver/Gold layers and quality../agendamento-retry-dlq.md— scheduling, retry/backoff and DLQ../custo-limites-seguranca.md— cost, limits and workspace security
Last review: 2026-10-04. Datasheet automatically generated from the product's connector catalog.