Get past meeting with the Zoom API

Returns the details of a meeting that already ended: start and end time, duration and participants count. Only meetings of the last year.

Identifier
zoom_get_past_meeting

The request

POST https://connect.reportei.com/api/tools/zoom_get_past_meeting/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "meetingId": "<meetingId>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
meetingIdstringYesMeeting ID from List meetings with type previous_meetings, for its latest instance, or the UUID of one instance from List recordings. A UUID that starts with / or contains // must be URL-encoded once before it is sent here.

Supported connections

Your customer connects their Zoom account once, with one of the modes below. The same connection serves every tool of the toolkit.

OAuth with your product's app

You register your product's OAuth app once, with POST /api/merchants/credentials/zoom, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/zoom_get_past_meeting. It becomes your agent's tool definition with no conversion.

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.