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
Get started with Agenda API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"get appointment by id"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Agenda API API.
get appointment by ID
creates an appointment
searches appointments
updates all the fields of an appointment
deletes an appointment
GET STARTED
Not supported: Does not handle payments, communications, or crm — use for productivity only.
Jentic publishes the only available OpenAPI specification for Agenda API, keeping it validated and agent-ready.
This API allows a front-end application to interact with the calendars of sales representatives. The API exposes 17 endpoints.
Patterns agents use Agenda API 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
17 endpoints — this api allows a front-end application to interact with the calendars of sales representatives.
METHOD
PATH
DESCRIPTION
/appointments/{id}
get appointment by ID
/appointments
creates an appointment
/appointments
searches appointments
/appointments
updates all the fields of an appointment
/appointments
deletes an appointment
/appointments/{id}/close/{close_reason_id}
updates the status of an appointment
/recurring_appointments/{id}
get recursion by ID
/recurring_appointments
creates a recurring pattern
/appointments/{id}
get appointment by ID
/appointments
creates an appointment
/appointments
searches appointments
/appointments
updates all the fields of an appointment
/appointments
deletes an appointment
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.
Alternatives and complements available in the Jentic catalogue.
Asana
Alternative productivity API
Choose Asana when you need a different approach to productivity operations
Monday
Alternative productivity API
Choose Monday when you need a different approach to productivity operations
Clickup
Complementary productivity API
Choose Clickup when you need a complementary approach to productivity operations
Specific to using Agenda API 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.
/appointments/{id}/close/{close_reason_id}
updates the status of an appointment
/recurring_appointments/{id}
get recursion by ID
/recurring_appointments
creates a recurring pattern