--- title: "Telefone Operadora" description: "API Telefone Operadora - Descubra a operadora em segundos" lang: en canonical: https://doc.apibrasil.io/apis/creditos/b5b42e9f-46c3-4713-aa72-c6df3c189059 markdown: https://doc.apibrasil.io/apis/creditos/b5b42e9f-46c3-4713-aa72-c6df3c189059.md source: apibrasil-documentation --- # Telefone Operadora > API Telefone Operadora - Descubra a operadora em segundos - **Category:** Messaging - **Billing:** per query, with the Bearer Token only - **Price:** R$0.04 per query - **Limit:** 990,000 per month - **Registration:** requires a CNPJ - **Version:** v2 - **Published by:** APIBrasil - **OpenAPI specification:** https://doc.apibrasil.io/apis/creditos/b5b42e9f-46c3-4713-aa72-c6df3c189059/openapi.json ## How to call **Base address:** `https://gateway.apibrasil.io/api/v2` Authentication: the `Authorization: Bearer ` 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/telefone/credits API Telefone Operadora - Descubra operadora e histórico com rapidez A API Telefone Operadora permite consultar instantaneamente a operadora atual de qualquer telefone, verificar informações de portabilidade e acessar o histórico de movimentações entre operadoras, tudo por meio de uma integração simples e rápida. Ideal para inteligência de crédito, e-commerce, serviços financeiros e sistemas antifraude, ela entrega dados confiáveis no retorno da requisição POST ao endpoint de credits. Valorize seu negócio, aumente a assertividade em suas validações e automatize processos essenciais, integrando facilmente esses dados valiosos ao seu sistema e potencializando sua análise e tomada de decisão. - **Method:** `POST` - **Address:** `https://gateway.apibrasil.io/api/v2/consulta/telefone/credits` - **Route version:** v2 **Headers** | Header | Value | | --- | --- | | `Content-Type` | `application/json` | | `Authorization` | `Bearer $APIBRASIL_TOKEN` | **Request body** ```json { "tipo": "telefone-operadora", "homolog": false, "numbers": [ "11999999998" ], "options": { "webhook": false, "webhook_url": "https://webhook.site/c52e999e-196d-44aa-9e8a-885192b61541", "retries": 0, "retry_delay": 1 } } ``` **In cURL** ```bash curl -X POST "https://gateway.apibrasil.io/api/v2/consulta/telefone/credits" \ -H "Content-Type: application/json" \ -H "Authorization: Bearer $APIBRASIL_TOKEN" \ -d '{"tipo":"telefone-operadora","homolog":false,"numbers":["11999999998"],"options":{"webhook":false,"webhook_url":"https://webhook.site/c52e999e-196d-44aa-9e8a-885192b61541","retries":0,"retry_delay":1}}' ``` 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": "", "email": "", "cellphone": "", "notification": "yes" }, "balance": "7.536,160", "error": false, "message": "Requisicao processada com sucesso", "response": { "request_uuid": "b5b42e9f-46c3-4713-aa72-c6df3c189059", "elapsed_seconds": 0, "results": [ { "telefone": "11999999998", "historico": [ { "prestadora": "Vivo", "razao_social": "VIVO S.A", "data": "", "mensagem": "Prestadora Origem" }, { "prestadora": "TIM S.A.", "razao_social": "TIM S.A.", "data": "01/09/2017 12:00", "mensagem": "Portabilidade Numérica" }, { "prestadora": "Vivo", "razao_social": "VIVO S.A", "data": "27/10/2017 20:00", "mensagem": "Portabilidade Numérica" }, { "prestadora": "Claro", "razao_social": "CLARO S.A.", "data": "03/08/2023 08:01", "mensagem": "Portabilidade Numérica" }, { "prestadora": "Vivo", "razao_social": "VIVO S.A", "data": "20/09/2023 12:08", "mensagem": "Portabilidade Numérica" } ] } ], "message": "Consulta realizada com sucesso", "numbers": [ "11999999998" ] }, "tax": "0,040", "valor_consulta": 0.04, "api_limit_for": "credit" } ``` ## 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/b5b42e9f-46c3-4713-aa72-c6df3c189059/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/b5b42e9f-46c3-4713-aa72-c6df3c189059