List meetings with the Webex API

Lists the meetings of the user in a date window of up to 7 days by default, with id, title, start, end, webLink and state. Without meetingType it returns meeting series. Webex pages with a Link header that this connection does not return: narrow from and to instead.

Identifier
webex_list_meetings

The request

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

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "meetingType": "meetingSeries"
  }
}

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
meetingTypestringNomeetingSeries, the default, for the series; scheduledMeeting for each upcoming occurrence; meeting for meetings that already happened or are happening.Values: meetingSeries, scheduledMeeting, meeting
statestringNoOnly meetings in this state. An ended meeting shows up about 15 minutes after it ends.Values: active, scheduled, ready, lobby, inProgress, ended, missed, expired
fromstringNoStart of the window, ISO 8601. The default is now, or 7 days ago for meetingType meeting.
tostringNoEnd of the window, exclusive, ISO 8601. The default is 7 days after from, or now for meetingType meeting.
maxintegerNoMeetings in the response, up to 100. The default is 10.

Supported connections

Your customer connects their Webex 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/webex, 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/webex_list_meetings. 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.