Skip to content

API reference

Get recently ended meeting

meetings.GetRecentlyEndedMeetingReadMember delegation

Find your most recently ended hosted meeting from the last five minutes. Returns meeting_id: null when none qualifies.

POST/v1/operations/meetings.GetRecentlyEndedMeeting
On this page

Access & visibility

Allow meetings.GetRecentlyEndedMeeting on your API key. Resource read permissions: core:Meeting.

Acting member required. Send Brigg-Act-As with an approved member account ID. The key supplies permissions; the member selects whose data is used.

The selected member must be active and approved by the credential. This selects whose private data is used; the credential supplies permissions. Private ownership and project boundaries still apply.

Set up authentication · Choose permissions

Request

No parameters. Send an empty JSON object ({}).

Response

Returns 200 OK with a JSON body.

meeting_idstring or nullRequired

Meeting identifier.

Errors & retries

This operation reads data. It needs no idempotency key and can be retried after a transient failure.

For rate limits, follow the server’s retry guidance and back off. See HTTP errors and safe retries and limits.

HTTP status Code What to do
400 invalid_json Send a JSON object with Content-Type: application/json.
400 invalid_input Check the request fields and types.
401 invalid_key The workspace API key is missing, invalid or revoked.
403 forbidden Check the key’s operation and resource grants. Supply Brigg-Act-As with a member authorized by the key’s delegation grant. The selected member must be active and approved by the credential. This selects whose private data is used; the credential supplies permissions. Private ownership and project boundaries still apply.
404 not_found The requested operation or resource is not available to this credential.
429 rate_limited Wait for Retry-After before retrying.

Next steps

Download OpenAPI · Versioning & retirement

JSON schemas

Use the complete schemas for validation or client generation.

Full request JSON schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false,
  "examples": [
    {}
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "meeting_id": {
      "type": [
        "string",
        "null"
      ],
      "description": "Meeting identifier."
    }
  },
  "required": [
    "meeting_id"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "meeting_id": "e_meeting_kickoff"
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.