canonical: https://jentic.com/apis/swaggerhub.microsoftpichet/base-mandat

# Microsoftpichet Base Mandat

API For Pichet Base Mandat. The API exposes 2 endpoints.

## For AI agents

Programmatically update progress of folder (signing, all signed, canceled), create a new sale. Covers 2 operations.

## Scope

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

## Capabilities

- Update progress of folder (signing, all signed, canceled)
- Create a new sale
- Integrate Base Mandat into automated workflows
- Query and filter Base Mandat records by parameters
- Monitor Base Mandat operational status and events

## Use cases

### Developer Tools Operations

Use the Base Mandat to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including update progress of folder (signing, all signed, canceled), create a new sale.

Example prompt: Call POST /docapost-folder/update to update progress of folder (signing, all signed, canceled)

### Data Retrieval and Monitoring

Query Base Mandat resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Base Mandat endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Base Mandat 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 'update progress of folder (signing, all signed, canceled)', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /docapost-folder/update | Update progress of folder (signing, all signed, canceled) |
| POST | /sales | Create a new sale |

## Key resources

- **docapost-folder** — Operations related to docapost-folder
- **sales** — Operations related to sales

## Why Jentic

- **Setup:** Wiring Base Mandat by hand means mapping its folder-update and sales routes, coding each POST, and handling retries yourself. Through Jentic you install once, import Base Mandat from the API Directory, store any host details once, and your agent calls it.
- **Permission scoping:** This API carries its folder and sales targets in the request body rather than the URL path, so scope the agent to the operations it needs, such as recording a sale. You choose the operations it may call, so the folder-update path is not included unless you add it.
- **Credential handling:** Any access details for Base Mandat 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 'update a signing folder' or 'record a sale', and Jentic returns the matching Base Mandat 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 Base Mandat use?

The Base Mandat 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 update progress of folder (signing, all signed, canceled) with the Base Mandat?

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

### What are the rate limits for the Base Mandat?

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 update progress of folder (signing, all signed, canceled) through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'update progress of folder (signing, all signed, canceled)'. Jentic returns the matching Base Mandat operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Base Mandat have?

The Base Mandat exposes 2 endpoints covering docapost-folder, sales operations.

### Can I limit what my agent is allowed to do with the Base Mandat API?

Yes. Because you run Jentic One yourself, your own rules decide which Base Mandat operations and credentials the agent may use. This API has just two operations, POST /docapost-folder/update to advance a signing folder and POST /sales to record a sale, and it carries its folder and sales targets in the request body rather than the URL path. You can scope the agent to only the operation it needs, such as recording a sale, so the folder-update path is not available unless you add it.