---
title: "Renda Presumida"
description: "Renda mensal estimada de uma pessoa física pelo CPF, com a faixa de renda. Retorna o valor presumido da renda mensal, a faixa de renda e a data de referência do cálculo."
lang: en
canonical: https://doc.apibrasil.io/apis/creditos/aba7f010-97aa-4e3a-8000-1a317c0a5e38
markdown: https://doc.apibrasil.io/apis/creditos/aba7f010-97aa-4e3a-8000-1a317c0a5e38.md
source: apibrasil-documentation
---

# Renda Presumida

> Renda mensal estimada de uma pessoa física pelo CPF, com a faixa de renda. Retorna o valor presumido da renda mensal, a faixa de renda e a data de referência do cálculo.

- **Category:** Credit Analysis
- **Billing:** per query, with the Bearer Token only
- **Price:** R$1.98 per query
- **Limit:** 990,000 per month
- **Registration:** requires a CNPJ
- **Version:** v2
- **Published by:** APIBrasil
- **OpenAPI specification:** https://doc.apibrasil.io/apis/creditos/aba7f010-97aa-4e3a-8000-1a317c0a5e38/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

⚠️ Aviso: a consulta só é cobrada quando a resposta traz a faixa ou o valor presumido. Sem informação para a consulta, a resposta é HTTP 404 e não há cobrança.

Envie um POST com tipo=renda-presumida e o cpf (11 dígitos, com ou sem máscara; o dígito verificador é conferido). A resposta vem em data.credcadastral e traz o bloco renda_presumida, com faixa (faixa de renda), valor_presumido (renda mensal estimada) e data_referencia. Cada bloco tem o seu status_retorno (codigo 1 = bloco consultado com sucesso). Campo cpf ausente ou inválido é recusado com HTTP 400, sem cobrança. Fonte indisponível responde HTTP 502, 503 ou 504, também sem cobrança. Em homologação (homolog=true) a resposta é uma amostra fictícia, sem cobrança, para qualquer cpf válido.

- **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": "renda-presumida",
  "cpf": "12345678909",
  "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":"renda-presumida","cpf":"12345678909","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": "398,020",
  "balance_before": "400,000",
  "tax": "1,980",
  "status_code": 200,
  "error": false,
  "message": "Dados validos! Voce foi tarifado em R$ 1,98.",
  "valor_consulta": 1.98,
  "api_limit_for": "credit",
  "homolog": false,
  "data": {
    "credcadastral": {
      "renda_presumida": {
        "status_retorno": {
          "codigo": "1",
          "descricao": "CONSULTA CONCLUIDA COM SUCESSO"
        },
        "descricao": "RENDA PRESUMIDA",
        "faixa": "DE R$ 2.001 A R$ 4.000",
        "renda_anual": "",
        "mensagem": "",
        "data_referencia": "20260101",
        "valor_presumido": "3.000,00",
        "dados_cadastro_positivo": "N"
      }
    }
  }
}
```

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/aba7f010-97aa-4e3a-8000-1a317c0a5e38/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/aba7f010-97aa-4e3a-8000-1a317c0a5e38
