---
title: "Enriquecimento Lead"
description: "API Enriquecimento Lead - Mais dados qualificados a partir do e-mail ou do telefone"
lang: en
canonical: https://doc.apibrasil.io/apis/creditos/94f0dc20-0afc-481d-8383-b1b62859c111
markdown: https://doc.apibrasil.io/apis/creditos/94f0dc20-0afc-481d-8383-b1b62859c111.md
source: apibrasil-documentation
---

# Enriquecimento Lead

> API Enriquecimento Lead - Mais dados qualificados a partir do e-mail ou do telefone

- **Category:** Search & Collections
- **Billing:** per query, with the Bearer Token only
- **Price:** R$3.66 per query
- **Limit:** 990,000 per month
- **Registration:** requires a CNPJ
- **Version:** v2
- **Published by:** APIBrasil
- **OpenAPI specification:** https://doc.apibrasil.io/apis/creditos/94f0dc20-0afc-481d-8383-b1b62859c111/openapi.json

## How to call

**Base address:** `https://gateway.apibrasil.io/api/v2`

Authentication: the `Authorization: Bearer <token>` header. Nothing else.

With `homolog: true` in the body, the gateway answers from a fixed base, with the real shape of the response, and does not charge. The CPF 00000000000 belongs to that base and to nobody: use it in tests, never in production.

## Endpoints (1 endpoint)

### 1. POST /consulta/cpf/credits

API Enriquecimento Lead - Transforme e-mail ou telefone em insights de vendas em segundos

A API Enriquecimento Lead permite transformar um simples e-mail ou telefone em um perfil completo de lead, acelerando a qualificação comercial e aumentando a conversão. Com integração rápida via método POST na rota de consulta/cpf/credits, você conecta seu CRM, funil de vendas ou sistema de automação e recebe em tempo real dados enriquecidos para priorizar oportunidades de alto valor. O retorno da API traz informações estruturadas, prontas para uso imediato em segmentação, personalização de ofertas, scoring de leads e gatilhos automáticos. Ideal para times de marketing e vendas que precisam agir com precisão e escalar resultados sem complicar a operação de TI.

Como consultar: envie um POST com tipo=enriquecimento-de-lead e o campo email ou o campo telefone (apenas um dos dois por consulta). Embora a rota seja consulta/cpf/credits, o CPF não é dado de entrada: ele vem no retorno, junto com nome, telefones, e-mails e endereços do lead. Use homolog=true para testar sem tarifar.

- **Method:** `POST`
- **Address:** `https://gateway.apibrasil.io/api/v2/consulta/cpf/credits`
- **Route version:** v2

**Headers**

| Header | Value |
| --- | --- |
| `Content-Type` | `application/json` |
| `Authorization` | `Bearer $APIBRASIL_TOKEN` |

**Request body**

```json
{
  "tipo": "enriquecimento-de-lead",
  "email": "email@gmail.com",
  "homolog": true
}
```

**In cURL**

```bash
curl -X POST "https://gateway.apibrasil.io/api/v2/consulta/cpf/credits" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $APIBRASIL_TOKEN" \
  -d '{"tipo":"enriquecimento-de-lead","email":"email@gmail.com","homolog":true}'
```

This endpoint accepts `homolog: true` in the body: the response comes back with valid data, `api_limit_for` equal to `homolog` and no charge.

**Sample response, from the catalog**

```json
{
  "user": {
    "first_name": "[omitido]",
    "email": "[omitido]",
    "cellphone": "[omitido]",
    "notification": "yes"
  },
  "balance": "108,300",
  "balance_before": "108,300",
  "tax": "0,000",
  "status_code": 200,
  "error": false,
  "message": "Dados validos em homologacao! Voce nao foi tarifado e a requisicao nao foi contabilizada.",
  "valor_consulta": 0,
  "api_limit_for": "homolog",
  "homolog": true,
  "data": {
    "cpf": "000.000.000-00",
    "dataNascimento": "15/04/1991 00:00:00",
    "emails": [
      {
        "enderecoEmail": "[omitido]"
      },
      {
        "enderecoEmail": "[omitido]"
      },
      {
        "enderecoEmail": "[omitido]"
      }
    ],
    "enderecos": [
      {
        "bairro": "JARDIM DAS FLORES",
        "cep": "01310-000",
        "cidade": "SAO PAULO",
        "complemento": "APTO 31",
        "logradouro": "RUA LUIZ BARBOSA",
        "numero": "120",
        "uf": "SP"
      },
      {
        "bairro": "PARQUE HORIZONTE",
        "cep": "31510-220",
        "cidade": "BELO HORIZONTE",
        "complemento": null,
        "logradouro": "AVENIDA DO SOL",
        "numero": "450",
        "uf": "MG"
      },
      {
        "bairro": "VILA DO LAGO",
        "cep": "30120-330",
        "cidade": "BELO HORIZONTE",
        "complemento": "CASA 04",
        "logradouro": "RUA DAS ACACIAS",
        "numero": "78",
        "uf": "MG"
      }
    ],
    "idade": 34,
    "nome": "ALICIA MENDES HOMOLOG",
    "nomeMae": "SILVIA MENDES DE ARAUJO",
    "rendaEstimada": "4200",
    "rendaFaixaSalarial": "Faixa 3 salarios minimos",
    "sexo": "Feminino",
    "signo": "Gemeos",
    "telefones": [
      {
        "operadora": "Homolog Telecom",
        "telefoneComDDD": "(31) 988870002",
        "telemarketingBloqueado": null,
        "tipoTelefone": "Celular",
        "whatsApp": true
      },
      {
        "operadora": "Homolog Telecom",
        "telefoneComDDD": "(31) 34440055",
        "telemarketingBloqueado": null,
        "tipoTelefone": "Residencial",
        "whatsApp": false
      },
      {
        "operadora": "Homolog Telecom",
        "telefoneComDDD": "(31) 998820033",
        "telemarketingBloqueado": null,
        "tipoTelefone": "Celular",
        "whatsApp": true
      }
    ]
  }
}
```

In the sample responses, the fields of the account that generated the sample (`user.first_name`, `user.email`, `user.cellphone`) come out as `[omitido]`. The rest is what the catalog publishes.

## Pitfalls: what an integration gets wrong without warning

Established from the responses the catalog itself publishes. In every one of them the code works on the happy path and fails silently everywhere else:

1. **The error arrives in the BODY, with HTTP 200.**
   The response carries a boolean `error` field and a `message`. Checking only `response.ok` or the HTTP status lets a failure through as a success. ALWAYS check `error === false` before reading `data`.

2. **`balance`, `tax` and `extra_charges.total` are STRINGS in Brazilian format — and the format varies between APIs.**
   Values seen in the catalog: `"154,380"`, `"497,84"`, `"0,000"` and `"0.19"`. Comma in some, dot in another; three decimal places in some, two in another. In JavaScript, `parseFloat("154,380")` returns `154` and drops the cents with no error at all, and `Number("154,380")` returns `NaN`. Write a converter that handles both separators, and never use these fields in a financial decision without converting them.

3. **Every call costs money.**
   Blind retries multiply the bill. Never automatically repeat a 4xx: a bad parameter repeated is still bad, and still charged. Retry only timeouts and 5xx, with exponential backoff and a small attempt ceiling.

4. **HTTP 402 means insufficient balance, and retrying does not fix it.**
   It is the one status that needs a human — a top-up. Treat it as a terminal error with its own message, and do not lump it in with generic 4xx.

5. **`extra_charges` bills on top of the lookup price.**
   When the body asks for add-on services, the response lists each one with its price plus a `total` that is NOT included in the base amount. If you show cost to an end user, add both.

## See also

- OpenAPI specification: https://doc.apibrasil.io/apis/creditos/94f0dc20-0afc-481d-8383-b1b62859c111/openapi.json
- API catalog: [API catalog](https://doc.apibrasil.io/apis.md)
- Official SDKs: [Official SDKs](https://doc.apibrasil.io/sdks.md)
- Documentation index: https://doc.apibrasil.io/llms.txt
- HTML version of this page: https://doc.apibrasil.io/apis/creditos/94f0dc20-0afc-481d-8383-b1b62859c111