Skip to main content
PATCH
/
calendar
/
scheduled_bots
/
{bot_id}
Reschedule Bot
curl --request PATCH \
  --url https://api.meestream.ai/api/v1/calendar/scheduled_bots/{bot_id} \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "scheduled_join_time": "2023-11-07T05:31:56Z"
}
'
{
  "success": true,
  "message": "<string>",
  "bot_id": "<string>",
  "scheduled_join_time": "2023-11-07T05:31:56Z"
}

​
Overview

This endpoint allows you to reschedule a bot that was created with a scheduled join time. You can update the scheduled_join_time to a new date and time, and the bot will join the meeting at the newly specified time.

​
Use Cases

  • Meeting Time Changed: When a meeting is rescheduled, update the bot’s join time accordingly
  • Delay Bot Join: Push back the bot’s join time if the meeting starts later than expected
  • Advance Bot Join: Move up the bot’s join time if the meeting starts earlier

​
Request Body

The request body should contain the new scheduled join time: 
{
  "scheduled_join_time": "2025-11-09T16:00:00+05:30"
}

​
Field Description

FieldTypeRequiredDescription
scheduled_join_timestringYesISO 8601 formatted datetime with timezone offset indicating when the bot should join the meeting

​
Date Format

The scheduled_join_time must be in ISO 8601 format with timezone offset: Format: YYYY-MM-DDTHH:mm:ss±HH:MM Examples:
  • 2025-11-09T16:00:00+05:30 (4:00 PM IST)
  • 2025-11-09T10:30:00-05:00 (10:30 AM EST)
  • 2025-11-09T15:00:00+00:00 (3:00 PM UTC)

​
Response

​
Success Response

{
  "success": true,
  "message": "Bot rescheduled successfully",
  "bot_id": "5b0ff6e7-3cea-4c9f-a6b4-851c5f11cf4f",
  "scheduled_join_time": "2025-11-09T16:00:00+05:30"
}

​
Error Responses

​
Bot Not Found

{
  "error": "Bot not found",
  "status_code": 404
}

​
Invalid Date Format

{
  "error": "Invalid date format. Please use ISO 8601 format with timezone",
  "status_code": 400
}

​
Bot Already Joined

{
  "error": "Cannot reschedule bot that has already joined the meeting",
  "status_code": 400
}

​
Important Notes

  • The bot must have been created with a scheduled join time using the join_at parameter in the Create Bot endpoint
  • You can only reschedule bots that haven’t joined the meeting yet
  • The new scheduled time must be in the future
  • The timezone offset is required and should match your desired meeting timezone

Authorizations

​
Authorization
string
header
required

All API endpoints are authenticated using API Keys. The key should be included in the 'Authorization' header, prefixed with 'Token '. Example: 'Authorization: Token YOUR_API_KEY'.

Path Parameters

​
bot_id
string
required

The BotID of the bot to reschedule.

Body

application/json
​
scheduled_join_time
string<date-time>
required

ISO 8601 formatted datetime with timezone offset indicating when the bot should join the meeting

Response

Bot rescheduled successfully.

​
success
boolean
required

Whether rescheduling was successful

​
message
string
required

Success message

​
bot_id
string
required

The bot ID that was rescheduled

​
scheduled_join_time
string<date-time>
required

The new scheduled join time