canonical: https://jentic.com/apis/swaggerhub.tsp7/integrao-talktelecom-tsp

# Tsp7 Integração Talktelecom TSP

Esta é a documentação disponibilizada para utilização da Talktelecom , para obtenção de dados , geração de acordos e inclusão de históricos. The API exposes 5 endpoints.

## For AI agents

Programmatically detalhesdividaparelado, geranegociacao. Covers 5 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- detalhesDividaParelado
- geraNegociacao
- adicionaHistorico
- valoresNegociação
- Monitor Integração Talktelecom TSP operational status and events

## Use cases

### Developer Tools Operations

Use the Integração Talktelecom TSP to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including detalhesdividaparelado, geranegociacao, geranegociacaoparcelada.

Example prompt: Call GET `/detalhes_divida_parcelado/{id_contrato}/{qntd_parcelas}/{valor_entrada}` to detalhesdividaparelado

### Automated Dados Management

Automate dados operations by combining multiple Integração Talktelecom TSP endpoints. Agents can geranegociacao and then geranegociacaoparcelada in a single workflow.

Example prompt: Call GET `/gera_acordo/{opcao}/{id_contrato}` to geranegociacao, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Integração Talktelecom TSP endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'detalhesdividaparelado', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/detalhes_divida_parcelado/{id_contrato}/{qntd_parcelas}/{valor_entrada}` | detalhesDividaParelado |
| GET | `/gera_acordo/{opcao}/{id_contrato}` | geraNegociacao |
| GET | `/gera_negociacao_parcelado/{id_contrato}/{qntd_parcelas}/{valor_entrada}` | geraNegociacaoParcelada |
| GET | `/historico/{id_contrato}/{id_ocorrencia}/{observacao}/{telefone}` | adicionaHistorico |
| GET | `/valores_negociacao/{contrato}` | valoresNegociação |

## Key resources

- **Dados** — Dados do cliente
- **Negociação** — Valores para negociação
- **Histórico** — Adicionar histórico

## Why Jentic

- **Setup:** Wiring the Talktelecom TSP integration by hand means pointing at its tsprecuperadora.com.br host and building your own retries across the negotiation and agreement endpoints, even though it exposes no auth scheme. Through Jentic you install once, import this API from the API Directory, store the connection details once, and your agent calls it.
- **Permission scoping:** This API puts the contract id in the URL path (`/gera_acordo/{opcao}/{id_contrato}`), so a rule can pin your agent to one contract: it can read that contract's negotiation values and generate its agreements and nothing else. Because you pick the allowed operations, the agent only runs the negotiation calls you authorize.
- **Credential handling:** Any connection details for the Talktelecom TSP integration are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get negotiation values for a contract' or 'generate an installment agreement', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Integração Talktelecom TSP use?

The Integração Talktelecom TSP uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I detalhesdividaparelado with the Integração Talktelecom TSP?

Yes. Use the GET `/detalhes_divida_parcelado/{id_contrato}/{qntd_parcelas}/{valor_entrada}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Integração Talktelecom TSP?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I detalhesdividaparelado through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'detalhesdividaparelado'. Jentic returns the matching Integração Talktelecom TSP operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Integração Talktelecom TSP have?

The Integração Talktelecom TSP exposes 5 endpoints covering dados, negociação, histórico operations.

### Can I limit what my agent is allowed to do with the Integração Talktelecom TSP?

Yes. Jentic One is self-hosted, so your own rules decide which operations and credentials the agent may use with the Integração Talktelecom TSP. Because the contract id sits in the URL path, such as GET `/gera_acordo/{opcao}/{id_contrato}`, you can pin the agent to a single contract and allow only the calls you choose, for example reading negotiation values with GET `/valores_negociacao/{contrato}` while blocking agreement generation. Any operation you do not authorize stays off limits.