---
title: "Consulta PEP Parentes"
description: "API Consulta PEP Parentes - Reduza riscos com análise ampliada de relacionamentos"
lang: en
canonical: https://doc.apibrasil.io/apis/creditos/33890aff-d246-4803-b3c3-8c11654fc378
markdown: https://doc.apibrasil.io/apis/creditos/33890aff-d246-4803-b3c3-8c11654fc378.md
source: apibrasil-documentation
---

# Consulta PEP Parentes

> API Consulta PEP Parentes - Reduza riscos com análise ampliada de relacionamentos

- **Category:** Fraud Analysis
- **Billing:** per query, with the Bearer Token only
- **Price:** R$0.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/33890aff-d246-4803-b3c3-8c11654fc378/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 Consulta PEP Parentes - Blindagem contra riscos com análise de parentesco político

A API Consulta PEP Parentes permite identificar, a partir do CPF informado via requisição POST, se o indivíduo possui parentes classificados como Pessoas Expostas Politicamente, fortalecendo seus controles de compliance e prevenção à lavagem de dinheiro. Com integração rápida ao seu sistema pela action técnica consulta/cpf/credits, você passa a consumir em tempo real dados estruturados sobre vínculos de parentesco com PEPs, prontos para automação de regras internas. O retorno da API entrega informações objetivas que podem ser usadas para enriquecer cadastros, qualificar análises de risco, apoiar decisões de crédito e cadastro, além de reforçar políticas de KYC e onboarding digital. Assim, sua empresa ganha agilidade, segurança regulatória e maior confiança nas relações com clientes e parceiros.

- **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
{
  "cpf": "00000000000",
  "tipo": "pessoa-exposta-politicamente-parentesco",
  "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 '{"cpf":"00000000000","tipo":"pessoa-exposta-politicamente-parentesco","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",
    "dataConsulta": "16/04/2026 10:58:20",
    "funcao": null,
    "nome": "USUARIO HOMOLOGACAO TESTE",
    "orgao": null,
    "parentescosPEP": [],
    "pep": false,
    "relacionadoComPEP": null,
    "status": "Usuario de homologacao nao identificado como PEP ou relacionado."
  }
}
```

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/33890aff-d246-4803-b3c3-8c11654fc378/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/33890aff-d246-4803-b3c3-8c11654fc378