canonical: https://jentic.com/apis/calendarhero.com/calendarhero

# CalendarHero API

The CalendarHero API schedules meetings and manages the people and conversations around them for a meeting-automation assistant. You read and update the user profile and connected directories, manage contacts, and work with meetings, their categories, and follow-up tasks. Search operations look up records across the account, webhooks notify your app when meeting events occur, and a messaging operation handles web conversation threads.

## For AI agents

Schedule and manage meetings, contacts, follow-up tasks, and webhooks for a CalendarHero account. Authenticates with an API token sent in the Authorization header.

## Scope

Does not handle payments, video conferencing, or email marketing. Use for scheduling meetings and managing their contacts and follow-up tasks only.

## Capabilities

- Schedule and manage meetings and their categories
- Create and track follow-up tasks on a meeting
- Manage contacts and look them up across the account
- Read and update the user profile and connected directories
- Subscribe to webhooks for meeting events
- Handle web conversation messages

## Use cases

### Agent Meeting Scheduling

An AI agent connected through Jentic creates a meeting, attaches follow-up tasks, and links the right contact, so a scheduling assistant runs without a person clicking through the app. Because contacts and meetings are separate resources, the agent can reuse a known contact when booking.

Example prompt: Schedule a 30-minute meeting with the contact named Jordan and add a follow-up task to send notes

### Contact-Linked Follow-ups

An assistant creates follow-up tasks on a meeting and ties them to the contacts involved, so action items are tracked against the right people after a call. The meeting-tasks operations let an agent add, list, and remove tasks as the follow-up progresses.

Example prompt: Create two follow-up tasks on today's client meeting and link them to that client's contact

### Webhook-Driven Meeting Sync

An integration subscribes to meeting webhooks so an external system is notified when a meeting is created or changed, keeping a CRM or planner in sync without polling. A sample payload operation helps an agent set up the handler before going live.

Example prompt: Subscribe to the new-meeting webhook and confirm the handler with the sample payload

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/user` | Get the user profile |
| GET | `/contact` | List contacts |
| POST | `/contact` | Create a contact |
| GET | `/meeting` | List meetings |
| POST | `/meeting/tasks` | Create a meeting follow-up task |
| GET | `/search` | Search records across the account |
| GET | `/provider` | Get the connected provider |

## Key resources

- **Meetings** — Create and manage meetings, their categories, and follow-up tasks
- **Contacts** — Create, count, look up, and remove contacts
- **User** — Read and update the profile and connected directories
- **Webhooks** — Subscribe to meeting events and inspect sample payloads
- **Search** — Look up records across the account

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 48 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 67 / 100
  - Developer Experience & Jentic Compatibility: 31 / 100
  - AI-Readiness & Agent Experience: 41 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 41 / 100
- **View full report:** https://jentic.com/apis/calendarhero.com/calendarhero/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the CalendarHero API by hand means handling its API token auth, keeping contacts, meetings, and tasks in sync, and registering webhook handlers for meeting events. Through Jentic you install once, import CalendarHero from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** You choose which operations your agent may call, so you can allow scheduling meetings and reading contacts while leaving contact deletion and directory changes out. Meeting and contact details travel in the request body, so rules bound which operations run rather than which record is touched.
- **Credential handling:** Your CalendarHero token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'schedule a meeting' or 'add a follow-up task', and Jentic returns the matching CalendarHero operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Calendly API** — Scheduling platform with booking links and availability rules
- **Cronofy API** — Calendar connectivity across Google, Microsoft, and Apple calendars
- **Acuity Scheduling API** — Appointment scheduling with intake forms and calendars

## FAQ

### Is there a CalendarHero MCP server?

You don't need an MCP server to give your agent the CalendarHero API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent can schedule meetings and manage contacts straight away, with no extra server to run and no tool definitions loaded into the agent's context.

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

Yes. You choose which operations your agent may call, so you can allow scheduling meetings and reading contacts while leaving contact deletion and profile changes out, and every call it makes is logged. That keeps a scheduling agent from editing your account settings.

### What authentication does the CalendarHero API use?

The CalendarHero API authenticates with an API token sent in the Authorization header per its OpenAPI spec. Through Jentic the token is stored encrypted by your own instance and added to each request at call time, so it never appears in the agent's prompt or logs.

### Can I attach follow-up tasks to a meeting with the CalendarHero API?

Yes. The meeting resource has operations to list, create, and remove follow-up tasks, so an agent can add action items to a meeting and track them afterward alongside the meeting's category and details.

### What are the rate limits for the CalendarHero API?

The OpenAPI spec does not specify rate limits for the CalendarHero API. For current limits, see the CalendarHero documentation at https://api.calendarhero.com.

### How do I schedule a meeting with the CalendarHero API through Jentic?

Import the CalendarHero API from the Jentic API Directory, then have your agent issue a request such as 'schedule a meeting with this contact'. Jentic matches the intent to the create-meeting operation and returns its input schema so the agent builds a valid request, with your stored token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.