Microsoftpichet Agenda API
Browse all Swaggerhub Microsoftpichet APIs★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingnone17 EndpointsREST
For Agents
Programmatically get appointment by id, creates an appointment. Covers 17 operations.
Use for: I need to appointment by id, I want to creates an appointment, Search for searches appointments, Find all updates all the fields of an appointment
Not supported: Does not handle payments, communications, or crm — use for productivity only.
This API allows a front-end application to interact with the calendars of sales representatives. The API exposes 17 endpoints.
Install Jentic One Beta
Connect the Agenda API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Agenda API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Agenda API.
get appointment by ID
creates an appointment
searches appointments
updates all the fields of an appointment
deletes an appointment
Use Cases
Patterns agents use Agenda API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'get appointment by id', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
17 endpoints — this api allows a front-end application to interact with the calendars of sales representatives.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Agenda API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'get appointment by id') and Jentic returns the matching Agenda API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Agenda API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Agenda API through Jentic.
What authentication does the Agenda API use?
The Agenda API uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED