Leia antes:
../conectores.md(state map) andfichas.md(index of fichas).
What it does#
Reads sales, subscriptions, and commissions history from the Hotmart Developers API and loads into the Bronze layer.
Supported ingestion modes:
- Nós buscamos — Nós buscamos os dados na sua fonte.
Purpose#
Bring Hotmart 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 of the product (connectors are part of all plans; the limit is the number of sources of the plan).
- Access: requires an active workspace — if the subscription is overdue, suspended or canceled, the run is blocked.
- Shutdown: ingestion runs can be temporarily turned off (maintenance or incident). When that happens, the screen indicates the feature is unavailable at the moment.
Prerequisites#
- A Hotmart account with access to the data you want to ingest.
- In Hotmart, go to Ferramentas → Credenciais Hotmart (developers.hotmart.com) and create a credential: it shows Client ID, Client Secret and a Basic token. Provide the Client ID and Client Secret — ingestia constructs the Basic from them and renews the access token by itself. The Basic field is optional, only for verification; none of the three is shown again.
Credentials#
Authentication method: Application credentials (client id/secret) exchanged for an access token.
Sensitive fields. They are encrypted (AES-256-GCM) and are never stored in the connection config, pipeline definition, export or DAG. By default the encrypted value is stored in the database; moving the credential from this connection to the external credential vault is an explicit choice, made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.
- Client Secret (
clientSecret) - Token Basic (optional) (
tokenBasic) — The 'Basic' value shown in the credentials. Optional: equivalent to the Client ID + Client Secret pair, which is what ingestia uses.
Secrets are never re-displayed and pass through redaction in every error/log (raw token, URL-encoded and in JSON).
Form fields#
| Field | Label | Type | Required | Notes |
|---|---|---|---|---|
clientId | Client ID | text | yes | Application credential generated on the Hotmart portal. |
clientSecret 🔒 | Client Secret | password/secret | yes | secret (encrypted; external vault optional) |
tokenBasic 🔒 | Token Basic (optional) | password/secret | no | secret (encrypted; external vault optional); The 'Basic' value shown in the credentials. Optional: equivalent to the Client ID + Client Secret pair, which is what ingestia uses. |
Step-by-step#
- In the Dados → Conexões menu, use Nova conexão.
- Choose Hotmart in the catalog.
- Fill 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#
Configuration example (all values are fictitious; secrets appear masked):
# Exemplo sintético (valores fictícios — não são credenciais reais)
clientId = exemplo-client-id-ficticio
clientSecret = •••••• (cifrado — nunca exibido)
tokenBasic = •••••• (cifrado — nunca exibido)Expected result#
Testar conexão returns the list of discovered tables/resources. After the first load, rows appear in your workspace's Bronze layer, ready for the pipeline.
Limits and costs#
- Pagination: hard cap 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.3 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 per workspace: each customer reads and writes only to 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 written. The external credential vault is optional and enabled per connection; without it, the encrypted value stays in the database. Changing the value here DOES NOT revoke the credential at the source.
- Redaction: every error/log goes through secret redaction (raw, URL-encoded and in JSON).
- Production does not mock: a path that would fall into mock trips the production guard (explicit failure instead of simulating success).
Common errors#
- Credencial recusada (401/403) — the provider rejected the credential: expired, revoked or lacks the necessary permission. Reconnect the source (the source and history are preserved; do not recreate the source).
- Limite de requisições (429) — the provider asked to wait. The extraction respects
Retry-Afterand retries; if it repeats, wait and reduce the schedule frequency. - Recurso não encontrado — check the resource identifier (account, object, report) and the granted permissions.
- Cursor de paginação travado — the extraction stops when the API cursor does not advance (anti-loop guard). If it happens in consecutive runs, open a support ticket stating the connector and the resource.
- Caminho de registros vazio — 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 the runs in connector observability (error rate, p50/p95, freshness).
- A schema change at the source is signaled by schema drift (new column = info; column removed/type changed = attention).
Related#
../conectores.md— catálogo de conectores por estado../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, caps and workspace security
Last revised: 2026-10-04. Ficha generated automatically from the product connectors catalog.