canonical: https://jentic.com/apis/swaggerhub.flaviamarco/api-envio-de-contratos

# Flaviamarco Contract Submission API

An API for submitting and managing contracts. The API exposes 2 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically access Contract Submission API resources. Covers 2 operations.

## Scope

Does not handle payments, communications, or crm - use for contract management only.

## Capabilities

- Access Contract Submission API resources via REST API
- Manage contract submission data programmatically
- Integrate Contract Submission API into automated workflows
- Query and filter Contract Submission API records by parameters
- Monitor Contract Submission API operational status and events

## Use cases

### Contract Submission Operations

Use the Contract Submission API to submit contracts programmatically. The API provides 2 endpoints for contract operations.

Example prompt: Execute a primary operation against the Contract Submission API

### Data Retrieval and Monitoring

Query Contract Submission API resources on a schedule to track changes, generate alerts, or feed downstream dashboards.

Example prompt: Poll the primary Contract Submission API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Contract Submission API endpoints through Jentic without managing credentials directly.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/contratos` | postContratos |
| PUT | `/contratos/{protocoloContrato}` | putContratos |

## Key resources

- **Contracts** — Operations related to Contratos

## Why Jentic

- **Setup:** Wiring the Contract Submission API by hand means running Unimed's OAuth 2.0 client credentials exchange against its access-token route, choosing among the sandbox and homologation gateway hosts, and refreshing the token yourself. Through Jentic you install once, import Contract Submission API from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** The Contract Submission API puts the contract protocol in the URL path (`/contratos/{protocoloContrato}`), so a rule can pin your agent to updating one contract. You choose the operations it may call, so submitting a new contract is not included unless you add it.
- **Credential handling:** Your Unimed client credentials 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 'submit a new contract' or 'update a contract by its protocol', and Jentic returns the matching Contract Submission API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Contract Submission API use?

The Contract Submission API uses oauth2 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.

### What are the rate limits for the Contract Submission API?

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 use contract submission API through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use contract submission API'. Jentic returns the matching Contract Submission API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Contract Submission API have?

The Contract Submission API exposes 2 endpoints covering contract submission operations.

### Does the Contract Submission API support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

### Can I limit what my agent is allowed to do with the Contract Submission API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations and which credentials your agent may use. You can allow only the update call (PUT `/contratos/{protocoloContrato}`) while withholding new contract submission (POST /contratos), and because the contract protocol sits in the URL path you can pin the agent to acting on a single contract. The client credentials you store stay under your control and are injected only for the operations you have approved.