Search recordings with the Webex API
Lists the recordings of meetings hosted by or shared with the user, newest first, with topic, playbackUrl and downloadUrl. Narrow by meetingId or by a from and to window; Webex pages with a Link header that this connection does not return.
- Identifier
- webex_search_recordings
The request
POST https://connect.reportei.com/api/tools/webex_search_recordings/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
| Parameter | Type | Required | Description |
|---|---|---|---|
| meetingId | string | No | Only the recordings of this meeting series, occurrence or past meeting, from List meetings. |
| from | string | No | Only recordings created from this moment, ISO 8601. |
| to | string | No | Only recordings created before this moment, ISO 8601. |
| topic | string | No | Only recordings with this topic, ignoring case. |
| max | integer | No | Recordings in the response, up to 100. |
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_search_recordings. It becomes your agent's tool definition with no conversion.
Other Webex tools
- List roomsGETLists the spaces the user is in, with id and title; in a 1:1 space the title is the other person. Webex pages with a Link header that this connection does not return, so ask for up to 1000 spaces at once with max.
- Create roomPOSTCreates a group space with the user as its first member and returns it with its id. Add people with Create membership.
- Create membershipPOSTAdds a person to a space by email, optionally as a moderator, and returns the membership. The user must be able to add people to that space.
- List messagesGETLists the messages of a space, newest first. Webex pages with a Link header that this connection does not return: for older messages, call again with before set to the created of the oldest message received.
- Send messagePOSTPosts a message as the user in a space, or in a 1:1 space with the person of toPersonEmail, and returns it with its id. Send roomId or toPersonEmail, and text or markdown.
- Update messagePUTEdits a message the user posted and returns it. A message takes up to 10 edits, and one with a file or card cannot be edited.
- Delete messageDELETEDeletes a message the user posted and answers 204 with no body.
- List meetingsGETLists 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.
See Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
