canonical: https://jentic.com/apis/swaggerhub.microsoftpichet/agenda-api

# Microsoftpichet Agenda API

This API allows a front-end application to interact with the calendars of sales representatives. The API exposes 17 endpoints.

## For AI agents

Programmatically get appointment by id, creates an appointment. Covers 17 operations.

## Scope

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

## Capabilities

- get appointment by ID
- creates an appointment
- searches appointments
- updates all the fields of an appointment
- deletes an appointment

## Use cases

### Productivity Operations

Use the Agenda API to perform productivity operations programmatically. The API provides 17 endpoints covering core functionality including get appointment by id, creates an appointment, searches appointments.

Example prompt: Call GET /appointments/{id} to get appointment by id

### Automated appointments Management

Automate appointments operations by combining multiple Agenda API endpoints. Agents can creates an appointment and then searches appointments in a single workflow.

Example prompt: Call POST /appointments to creates an appointment, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Agenda API 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 'get appointment by id', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /appointments/{id} | get appointment by ID |
| POST | /appointments | creates an appointment |
| GET | /appointments | searches appointments |
| PATCH | /appointments | updates all the fields of an appointment |
| DELETE | /appointments | deletes an appointment |
| PUT | /appointments/{id}/close/{close_reason_id} | updates the status of an appointment |
| GET | /recurring_appointments/{id} | get recursion by ID |
| POST | /recurring_appointments | creates a recurring pattern |

## Key resources

- **appointments** — Access appointment related information
- **recurring appointments** — Access recurring appointment related information
- **ref data** — Get referential data
- **metadata** — Get metadata

## Why Jentic

- **Setup:** Wiring the Agenda API by hand means mapping its appointment and recurring-appointment routes, coding GET, POST, PATCH, PUT, and DELETE, and handling retries yourself. Through Jentic you install once, import the Agenda API from the API Directory, store any host details once, and your agent calls it.
- **Permission scoping:** This API puts the appointment id in the URL path (/appointments/{id}, /appointments/{id}/close/{close_reason_id}), so a rule can pin your agent to reading or closing one appointment and nothing else. You choose the operations it may call, so destructive ones like appointment deletion are not included unless you add them.
- **Credential handling:** Any access details for the Agenda API 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 an appointment by id' or 'create a recurring appointment', and Jentic returns the matching Agenda API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the Agenda API use?

The Agenda API 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 get appointment by id with the Agenda API?

Yes. Use the GET /appointments/{id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Agenda 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 get appointment by id through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get appointment by id'. Jentic returns the matching Agenda API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Agenda API have?

The Agenda API exposes 17 endpoints covering appointments, recurring appointments, ref data operations.

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

Yes. Jentic One is self-hosted, so you set the rules that decide which Agenda API operations and credentials your agent may use. Because the appointment id sits in the URL path (GET /appointments/{id} and PUT /appointments/{id}/close/{close_reason_id}), you can pin the agent to reading or closing a single appointment and nothing more. You choose the operations it may call, so destructive ones like DELETE /appointments are excluded unless you add them.