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

# iMeetify API

Jentic publishes the only available OpenAPI specification for iMeetify API, keeping it validated and agent-ready. iMeetify is a meeting scheduling service that exposes endpoints for creating, listing, and cancelling meetings, plus availability and calendar lookups. The API targets sales tools, recruiting platforms, and internal apps that need to book a meeting against a host's connected calendars without redirecting users to a third-party scheduler page. The surface is compact - six endpoints - and uses an API key header for authentication.

## For AI agents

Schedule, list, and cancel meetings against a host's connected calendars and check availability through a small REST surface.

## Scope

Does not handle video conferencing, payment collection, or contact management - use for meeting scheduling and availability lookups only.

## Capabilities

- Create a meeting with a chosen host, time slot, and invitees
- List meetings on the account with filtering by status or host
- Retrieve a single meeting record by its identifier
- Cancel an existing meeting and notify attendees
- Check a host's availability for a candidate window
- List the calendars connected to the iMeetify account

## Use cases

### In-App Meeting Booking

SaaS apps that already authenticate users do not want to redirect them out to a public scheduler page. Calling /availability followed by /meetings booking inside the app keeps the booking flow on-brand and on-domain. iMeetify handles the calendar conflict checks via the host's connected calendars.

Example prompt: GET /availability for the host, present open slots to the user, then POST /meetings with the chosen slot and invitee details.

### Sales Outreach Automation

Sales tools that book follow-up meetings after a lead converts can automate the booking via the iMeetify API. The tool calls /availability, picks the next open 30-minute slot, and posts a /meetings creation with the lead's email. The booked meeting writes back to the rep's connected calendar automatically.

Example prompt: After a lead converts, GET /availability for the assigned rep, POST /meetings with the next open slot and the lead's email, and log the meeting ID on the lead record.

### Recruiting Interview Coordination

Recruiting platforms book interviews with multiple panel members. The platform queries /calendars and /availability for each panel member, finds an overlap, and creates the meeting once a slot is agreed. Cancelling and rescheduling go through DELETE `/meetings/{meeting_id}` so candidates always see fresh state.

Example prompt: GET /availability for each panellist, intersect the open windows, POST /meetings with the agreed slot, and DELETE `/meetings/{meeting_id}` on cancellation.

### Agent-Driven Calendar Booking

An AI scheduling assistant that reads emails and proposes meeting times can call iMeetify directly through Jentic. The agent reads the host's availability, proposes a slot, and creates the meeting once both sides confirm. Jentic keeps the API key vaulted and returns the booking schema so the agent fills only the slot, host, and invitee fields.

Example prompt: Search Jentic for 'schedule a meeting with iMeetify', execute /availability and /meetings POST, and confirm the booking ID back to the user.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/meetings` | Create a meeting |
| GET | `/meetings` | List meetings on the account |
| GET | `/meetings/{meeting_id}` | Retrieve a meeting by ID |
| DELETE | `/meetings/{meeting_id}` | Cancel a meeting |
| GET | `/availability` | Check host availability |
| GET | `/calendars` | List connected calendars |

## Key resources

- **Meetings** — Create, list, retrieve, and cancel meetings.
- **Availability** — Check a host's availability for candidate slots.
- **Calendars** — List the calendars connected to the iMeetify account.

## Why Jentic

- **Setup:** Wiring iMeetify by hand means setting up its X-API-Key header against api.imeetify.com and handling the meeting and availability lookups yourself. Through Jentic you install once, import the iMeetify API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** iMeetify puts the meeting id in the URL path (`/meetings/{meeting_id}`), so a rule can pin your agent to one meeting. You choose the operations it may call, so destructive ones like deleting a meeting are not included unless you add them.
- **Credential handling:** Your iMeetify API key is stored once, encrypted, by your own Jentic One instance and injected into the request header 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 'check availability', and Jentic returns the matching iMeetify operation with its input schema, including the slot and invitee fields, so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Calendly** — Calendly is a widely adopted scheduling platform with a richer API and webhook surface.
- **Google Calendar** — Google Calendar is the underlying calendar that iMeetify reads availability from for many users.
- **Zoom Meetings** — Zoom Meetings hosts the video conferencing link that scheduled meetings often use.

## FAQ

### Why is there no official OpenAPI spec for iMeetify API?

iMeetify does not publish a canonical OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call iMeetify via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the iMeetify API use?

The API uses an API key in a request header (ApiKey scheme). Through Jentic the key is held in the encrypted vault and added to the request at execute time, so the agent prompt never sees it.

### Can I check a host's availability before booking?

Yes. GET /availability returns open windows for the connected host's calendars, which you can present to the user before calling POST /meetings to confirm the booking.

### How do I cancel a meeting?

DELETE `/meetings/{meeting_id}` cancels the meeting and notifies the participants based on the host's iMeetify settings.

### How do I book a meeting through Jentic?

Run pip install jentic, search for 'schedule a meeting with iMeetify', load the /meetings POST schema, and execute with the host, slot, and invitee details. Jentic chains the availability check if requested.

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

The OpenAPI spec does not list explicit rate limits. Plan for normal scheduling-app traffic and back off on HTTP 429 responses if running bulk imports.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which iMeetify operations and credentials your agent may use. You can grant read-only calls like GET /availability, GET /calendars, and GET /meetings while withholding write and destructive operations such as POST /meetings or DELETE `/meetings/{meeting_id}` unless you explicitly add them. Since the meeting id sits in the URL path, a rule can also pin the agent to a single meeting so it cannot touch others.