Microsoftpichet Agenda API

Name: Agenda API
Brand: Agenda API
Availability: InStock

Browse all Swaggerhub Microsoftpichet APIs

★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingnone17 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.

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 | sh

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 instance

Jentic 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

GET STARTED

Start building with Agenda API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

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 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.

Microsoftpichet Agenda API

Connect the Agenda API to your agent

Capabilities

Start building with Agenda API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs