---
title: "Schedule bot"
method: POST
path: "/meetings/{event_id}/bot"
tags: ["meetings"]
---

# Schedule bot

`POST /meetings/{event_id}/bot`

## Request

- Base URL: `https://api.timeless.day/v1`
- URL: `https://api.timeless.day/v1/meetings/{event_id}/bot`
- Auth: HTTP bearer

Schedules the AI note-taker bot to join a specific upcoming event. The request is accepted and processed asynchronously — a `202` means the bot has been queued to join, not that it has joined yet. To send the bot to a link with no calendar event, use [Send bot to link](/api-reference/meetings/send-bot-to-link).

## Path parameters

- `event_id` string, required

## Response `202`

The bot has been queued to join the event.

- BotScheduleResponse: Acknowledgement that the bot schedule or cancel request was accepted and queued.
  - `event_id` string, required: The calendar event the bot request applies to.
  - `status` 'scheduling' | 'cancelling', required: Whether the bot is being scheduled or cancelled for the event.

## Other responses

- `401`: Authentication required.
- `403`: Usage limit exceeded. Upgrade your plan to schedule the bot.
- `404`: Event not found.
- `422`: Validation Error

## Changes

- **2026-11-03** `10a43448b654`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/timeless/apis/timeless-public-api/changes/meetings/:event_id/bot/post.md)

---

[API](https://skmtc.dev/timeless/apis/timeless-public-api.md) - [All operations](https://skmtc.dev/timeless/apis/timeless-public-api/llms.txt) - [OpenAPI document](https://skmtc.dev/timeless/apis/timeless-public-api/revisions/10a43448b654?raw)