/api/v1/meetings/check-nowCheck for new meetings
The Google Meet scripts connected to workspace that have Check now on run now instead of at their next run (every 5 minutes): Markdrop calls each script's web app with a key only it and the script have, the script sends what's new to the inbox as usual, and this waits for them (up to about 50 seconds; a script still sending then answers timeout, and its meetings arrive as it sends them). Members and up; once a minute per workspace (429 {error: "too_soon", retry_after, message}). 409 {error, message} with not_connected or not_set_up. Returns {ok, message, checked, failed, not_set_up, imported, attached, updated, not_ready, writing, remaining, connections}; each connection: {connected_by, mine, ok, error?, message?, found, sent, imported, attached, updated, not_ready, writing, remaining}. error is bad_key or no_key (the deployment runs an older script, or setup hasn't run since the update), too_soon, busy (a scheduled run is going), disconnected, failed, sign_in (Who has access isn't Anyone), not_script, unreachable or timeout. 6 a minute per person.
Guide: Check for new meetings
Code samples and Try itRequest body
#application/json, required
workspacestringRequiredFile it in this workspace: the workspace's id. Up to 40 characters.
Responses
#200OK.401No token, or the token is revoked or mistyped.422The request didn't validate.detaillists each problem, with where it is (loc) and why (msg).429Too many requests from your IP address. Wait the seconds inRetry-After.