agentOS API V3, Diary Call Group

Name: agentOS API V3, Diary Call Group API
Brand: agentOS API V3, Diary Call Group
Availability: InStock

★ Only Publicly Available SpecProductivityCalendar SchedulingapiKey, basic13 EndpointsREST

For Agents

Read diary allocations, book and update viewing appointments, manage recurring appointments, and search applicants for the agentOS lettings platform.

Quickstart

Get started with agentOS API V3, Diary Call Group 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:
"book agentos viewing appointment"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with agentOS API V3, Diary Call Group API.

Read available diary allocations for the next seven days for a given short-name tenant

Create, update, and delete a viewing or valuation appointment in a valid diary allocation

Cancel an existing appointment by ID and capture a cancellation reason

Submit feedback against a completed appointment for the agent or guest record

GET STARTED

Start building with agentOS API V3, Diary Call Group API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for agentOS API V3, Diary Call Group, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for agentOS API V3, Diary Call Group, keeping it validated and agent-ready. The agentOS Diary API is a lettings-and-property-management appointment platform: agents can read available diary allocations for the next seven days, create and update appointments, cancel and delete them, submit feedback, list recurring appointments, look up branches for a company, and search guest applicants by parameter. It is purpose-built for letting agents booking viewings rather than a generic calendar.

Use Cases

Patterns agents use agentOS API V3, Diary Call Group API for, with concrete tasks.

★ Property Viewing Booking Bot

Let prospective tenants book a viewing without phoning the branch. The agent reads /allocations to find open slots, posts the appointment via /appointment, and returns the confirmation. Replaces the back-and-forth voicemail loop and frees branch staff for higher-value calls.

GET /v3/diary/{shortName}/allocations for the next 7 days, then POST /v3/diary/{shortName}/appointment with the chosen slot and the applicant details.

Cancellation and Reschedule Workflow

Handle reschedule requests cleanly. The agent looks up the appointment via GET /appointment, cancels it via PATCH /appointment/{appointmentID}/cancel with a reason, then books the new slot with POST /appointment. Keeps the diary tidy and avoids the silent no-shows that come from leaving stale appointments on the calendar.

GET the existing appointment, PATCH /appointment/{appointmentID}/cancel with the reason, then POST /appointment with the new slot.

Post-Viewing Feedback Capture

Capture viewer feedback right after a viewing while it is fresh. The agent listens for completed-appointment events, posts a /appointment/feedback record, and surfaces sentiment back into the lettings CRM. Replaces the end-of-day spreadsheet that branch managers usually reconcile by hand.

POST /v3/diary/{shortName}/appointment/feedback with the appointmentId and the feedback payload after the appointment end time.

Branch Routing for a Multi-Site Agency

Route incoming booking requests to the right branch. The agent reads /company/branches to list active branches, picks the closest by postcode, and books the appointment under that branch's diary. Useful for agencies operating across multiple towns where a single booking line drops calls into the wrong branch today.

GET /v3/diary/{shortName}/company/branches, pick the branch by postcode proximity, then POST /v3/diary/{shortName}/appointment under that branchId.

AI Agent Lettings Assistant via Jentic

An AI agent built on Jentic talks to applicants in chat: it finds open slots, books the viewing, sends a confirmation, and submits feedback after. Jentic isolates the API key and basic-auth credentials so the agent never holds them between turns and surfaces the right operation by intent rather than path.

Through Jentic, search 'book agentos viewing', execute /allocations, then POST /appointment with the chosen slot and applicant details.

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for agentos api v3, diary call group, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v3/diary/{shortName}/allocations

Get available diary allocations for the next 7 days

POST

/v3/diary/{shortName}/appointment

Book an appointment in a valid allocation

PUT

/v3/diary/{shortName}/appointment

Update an existing appointment

DELETE

/v3/diary/{shortName}/appointment

Delete an existing appointment

PATCH

/v3/diary/{shortName}/appointment/{appointmentID}/cancel

Cancel an existing appointment

POST

/v3/diary/{shortName}/appointment/feedback

Submit appointment feedback

GET

/v3/diary/{shortName}/company/branches

List branches for the company

GET

/v3/diary/{shortname}/{branchID}/guest/search

Search applicants by guest parameters

GET

/v3/diary/{shortName}/allocations

Get available diary allocations for the next 7 days

POST

/v3/diary/{shortName}/appointment

Book an appointment in a valid allocation

PUT

/v3/diary/{shortName}/appointment

Update an existing appointment

DELETE

/v3/diary/{shortName}/appointment

Delete an existing appointment

PATCH

/v3/diary/{shortName}/appointment/{appointmentID}/cancel

Cancel an existing appointment

Why though Jentic?

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

Credential isolation

agentOS API keys and basic-auth credentials are stored encrypted in the Jentic vault. The agent receives a scoped execution capability — neither the `ApiKey` header value nor the basic credentials enter the LLM context or tool-call traces.

Intent-based discovery

Agents search Jentic with intents like 'book agentos viewing' or 'cancel appointment' and Jentic returns the matching Diary operation with its input schema, including the `{shortName}` and `{appointmentID}` path parameters, so the agent calls the right endpoint without parsing 13 paths by hand.

Time to first call

Direct agentOS Diary integration: 1-2 days to wire dual auth, model the short-name path parameter, and chain allocation-and-appointment flows. Through Jentic: under an hour to wire the first booking flow.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Calendly API

Calendly is a generic scheduling API that handles availability and bookings.

Pick Calendly for general-purpose scheduling across industries; pick agentOS Diary when the workflow is specifically lettings viewings with branches, applicants, and recurring property viewings.

Alternative

Acuity Scheduling API

Acuity Scheduling provides hosted appointment booking with calendars and forms.

Pick Acuity for hosted booking pages and consumer-friendly scheduling; pick agentOS Diary when the diary is part of a lettings CRM and applicant search matters.

Complementary

Typeform API

Typeform captures the applicant interest form before agentOS books the viewing slot.

Use Typeform to capture initial applicant details and agentOS Diary to book the viewing into a real branch slot from the same flow.

FAQs

Specific to using agentOS API V3, Diary Call Group API through Jentic.

Why is there no official OpenAPI spec for agentOS API V3, Diary Call Group?

letmc.com does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call agentOS API V3, Diary Call Group via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the agentOS Diary API use?

The Diary API supports two schemes: an API key in the `ApiKey` header and HTTP basic authentication. Through Jentic, both forms live encrypted in the credential vault and are applied to outgoing requests at execution time so they never enter the agent's prompt.

Can I book and cancel viewing appointments through the API?

Yes. POST /v3/diary/{shortName}/appointment books an appointment in a valid diary allocation, PUT updates an existing appointment, DELETE removes one outright, and PATCH /v3/diary/{shortName}/appointment/{appointmentID}/cancel cancels with a reason.

What are the rate limits for the agentOS Diary API?

Rate limits are not declared in the OpenAPI spec. Treat the API as a moderate-volume diary integration: read allocations once per applicant interaction rather than continuously polling, and rely on event flows for status updates where possible.

How do I find available appointment slots through Jentic?

Run `pip install jentic`, search 'find agentos diary allocations', and execute GET /v3/diary/{shortName}/allocations for the tenant short name. Jentic returns the open allocations ready for the agent to offer to the applicant.

Can I look up branches for a letting agency?

Yes. GET /v3/diary/{shortName}/company/branches lists all branches for the company, and GET /v3/diary/{shortName}/company/branches/{branchID} returns a specific branch by Object ID for routing appointments correctly.