canonical: https://jentic.com/apis/swaggerhub.racsystems/swaggerhub-racsystems

# Racsystems Aplicativo de Vendas

Documentação para definição do aplicativo de Vendas. The API exposes 19 endpoints secured with apiKey authentication.

## For AI agents

Programmatically criar contrato, listar profissões de cliente. Covers 19 operations with apiKey authentication.

## Scope

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

## Capabilities

- Criar contrato
- Listar profissões de cliente
- Alterar contrato atual
- Pagemento de parcelas atrasadas
- Monitor Aplicativo de Vendas operational status and events

## Use cases

### Developer Tools Operations

Use the Aplicativo de Vendas to perform developer tools operations programmatically. The API provides 19 endpoints covering core functionality including criar contrato, listar profissões de cliente, listar planos para o cliente.

Example prompt: Call POST /contracts to criar contrato

### Automated Autenticação Management

Automate autenticação operations by combining multiple Aplicativo de Vendas endpoints. Agents can listar profissões de cliente and then listar planos para o cliente in a single workflow.

Example prompt: Call GET `/contracts/jobs` to listar profissões de cliente, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Aplicativo de Vendas 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 apiKey tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/contracts` | Criar contrato |
| GET | `/contracts/jobs` | Listar profissões de cliente |
| GET | `/contracts/plans` | Listar planos para o cliente |
| GET | `/contracts/plans/services` | Listar serviços adicionais do plano |
| PUT | `/contracts/{id}` | Alterar contrato atual |
| POST | `/contracts/{id}/payments` | Pagemento de parcelas atrasadas |
| PUT | `/contracts/{id}/plans` | Alterar o plano do cliente |
| POST | `/contracts/{id}/signatures` | Enviar assinaturas do contrato |

## Key resources

- **Autenticação** — Operations related to Autenticação
- **Cliente** — Operations related to Cliente
- **Contrato** — Operations related to Contrato
- **Lead** — Operations related to Lead
- **Visita** — Operations related to Visita

## Why Jentic

- **Setup:** Wiring Aplicativo de Vendas by hand means placing its JWT token in the Authorization header, coding across its contract endpoints, and handling retries yourself. Through Jentic you install once, import Aplicativo de Vendas from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Aplicativo de Vendas puts the contract id in the URL path (`/contracts/{id}/...`), so a rule can pin your agent to one contract: it can read that contract and its plans and nothing else. You choose the operations it may call, so payment posting or signature creation is not included unless you add it.
- **Credential handling:** Your Aplicativo de Vendas token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a sales contract' or 'list contract plans', and Jentic returns the matching Aplicativo de Vendas 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 Aplicativo de Vendas use?

The Aplicativo de Vendas uses an API key passed in the `Authorization` header. 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 criar contrato with the Aplicativo de Vendas?

Yes. Use the POST /contracts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Aplicativo de Vendas?

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 criar contrato through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'criar contrato'. Jentic returns the matching Aplicativo de Vendas operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Aplicativo de Vendas have?

The Aplicativo de Vendas exposes 19 endpoints covering autenticação, cliente, contrato operations.

### Can I limit what my agent is allowed to do with the Aplicativo de Vendas API?

Yes. Because you run Jentic One yourself, your own rules decide which Aplicativo de Vendas operations and credentials the agent may use. The API puts the contract id in the URL path (`/contracts/{id}/...`), so you can pin the agent to a single contract and let it read only that contract and its plans. You also choose the operations it may call, so posting payments to `/contracts/{id}/payments` or creating signatures via `/contracts/{id}/signatures` stays off unless you explicitly allow it.