canonical: https://jentic.com/apis/swaggerhub.santanense/apis---santanense-x-ematex

# Santanense APIs - Santanense x Ematex

APIs de integração TOTVs Datasul - EMATEX. Alguns links úteis: - [Sigma](https://sigma.santanense.com.br) - [Institucional Santanense](https://www.santanense.com.br/). The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically consulta notas, consulta notas. Covers 8 operations with apiKey authentication.

## Scope

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

## Capabilities

- Consulta Notas
- Liberar Pedidos
- Envio de nora e Baixa estoque
- Query and filter APIs - Santanense x Ematex records by parameters
- Monitor APIs - Santanense x Ematex operational status and events

## Use cases

### Developer Tools Operations

Use the APIs - Santanense x Ematex to perform developer tools operations programmatically. The API provides 8 endpoints covering core functionality including consulta notas, consulta notas, consulta lotes da nota.

Example prompt: Call GET `/flex/ind/consultaNotas` to consulta notas

### Automated notas Management

Automate notas operations by combining multiple APIs - Santanense x Ematex endpoints. Agents can consulta notas and then consulta lotes da nota in a single workflow.

Example prompt: Call GET `/flex/ind/Wescd0001` to consulta notas, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call APIs - Santanense x Ematex 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 'consulta notas', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/flex/ind/consultaNotas` | Consulta Notas |
| GET | `/flex/ind/Wescd0001` | Consulta Notas |
| GET | `/flex/ind/Wescd0003` | Consulta Lotes da Nota |
| GET | `/flex/ind/pedidos` | Consulta Pedidos |
| POST | `/flex/ind/liberaPedidos` | Liberar Pedidos |
| GET | `/flex/ind/consultaSaldos` | Consulta saldos em estoque |
| POST | `/flex/ind/Wescd0002` | Envio de nora e Baixa estoque |
| POST | `/flex/ind/AtuCliValues` | Atualiza dados de clientes |

## Key resources

- **notas** — Notas
- **pedidos** — Pedidos
- **estoque** — Estoque
- **clientes** — Clientes

## Why Jentic

- **Setup:** Wiring APIs - Santanense x Ematex by hand means learning its x_api_key header scheme, wiring the key on every call to the pasoe.santanense.com.br host, and handling requests and retries yourself. Through Jentic you install once, import APIs - Santanense x Ematex from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The target for these operations travels in query or body parameters rather than the URL path, so scope the agent by operation: limit it to the operations it needs, such as querying invoices or checking balances. Writes like releasing orders stay out of the allowed set unless you add them.
- **Credential handling:** Your APIs - Santanense x Ematex key 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 'query invoices' or 'check stock balances', and Jentic returns the matching APIs - Santanense x Ematex 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 APIs - Santanense x Ematex use?

The APIs - Santanense x Ematex uses an API key passed in the `x_api_key` 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 consulta notas with the APIs - Santanense x Ematex?

Yes. Use the GET `/flex/ind/consultaNotas` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the APIs - Santanense x Ematex?

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 consulta notas through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'consulta notas'. Jentic returns the matching APIs - Santanense x Ematex operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the APIs - Santanense x Ematex have?

The APIs - Santanense x Ematex exposes 8 endpoints covering notas, pedidos, estoque operations.

### Can I limit what my agent is allowed to do with the Santanense Ematex API?

Yes. Because Jentic One is self-hosted, your own rules decide which of the eight operations the agent may call, and the target for each call travels in query or body parameters rather than the URL path, so you scope access by operation. You can allow read operations like GET `/flex/ind/consultaNotas` for querying invoices and GET `/flex/ind/consultaSaldos` for checking stock balances while keeping writes such as POST `/flex/ind/liberaPedidos` for releasing orders out of the allowed set. Your API key is stored encrypted by your own instance and injected only when a permitted operation runs, so raw credentials never reach the agent context.