API v2/Released Nov 17, 2026

v2.7.0Latest

Google Meet bots refused by Google end with BOT_REJECTED_BY_GOOGLE

Breaking
  • 1breaking
  • 3new
  • 3improved
  • 2fixed

This release contains breaking changes

Review the breaking changes before upgrading. See the versioning policy for how they are announced and supported.

Google Meet bots that Google itself turns away now end with their own error code, BOT_REJECTED_BY_GOOGLE, separate from bots that someone in the meeting declined. Integrators who match on BOT_NOT_ACCEPTED for Google Meet bots should read the breaking change below. Zoom and Microsoft Teams bots are unchanged.

Breaking Changes

  • error_code of Google Meet bots refused by Google — a guest bot that Google Meet refuses before anyone in the meeting can admit it now ends with BOT_REJECTED_BY_GOOGLE. Until now it ended with BOT_NOT_ACCEPTED, the same code as a bot declined by a participant. Who is affected: integrations that match on BOT_NOT_ACCEPTED in bot.failed webhooks, callbacks or bot details to detect every Google Meet bot that was not let in. What to do: handle BOT_REJECTED_BY_GOOGLE wherever you handle BOT_NOT_ACCEPTED, see error codes. The status stays bot_rejected in both cases, so integrations that match on the status need no change. Before: "error_code": "BOT_NOT_ACCEPTED" → After: "error_code": "BOT_REJECTED_BY_GOOGLE"

New Features

  • BOT_REJECTED_BY_GOOGLE — a new error code for Google Meet bots that Google refuses. These bots are not charged for the time spent waiting, since nobody in the meeting saw the request.
  • parent_id on each entry of updates in GET /public/status — links a follow-up update to the incident it belongs to, or is null for the incident itself.
  • The dashboard's bots list shows "Rejected by Google" for these bots and can filter on it.

Improvements

  • BOT_NOT_ACCEPTED on Google Meet now means that someone in the meeting declined the bot, and its description says so.
  • A Google Meet bot that is about to make another attempt no longer reports bot_rejected first. The bot_rejected status and its bot.status_change webhook are sent only when the outcome is final, or when a participant declined the bot.
  • The status returned by GET /public/status stays correct when an incident has follow-up updates or overlaps another incident.

Bug Fixes

  • A bot that was interrupted while being handed over to a new attempt, and whose handover failed, could keep a non-final status. It now ends as failed with an error code.
  • Eight outcomes appeared as "Unknown Error" in the dashboard's bots list, among them ZOOM_PASSCODE_REQUIRED, ZOOM_INVALID_PASSCODE, ZOOM_WEBINAR_REGISTRATION_REQUIRED and ZOOM_LOADING_STALLED. They now show their own label.

↩ All releases

On this page