Webex · Schema
queryRegistrants
CallingCollaborationCommunicationsEnterpriseMessagingVideo Conferencing
Properties
| Name | Type | Description |
|---|---|---|
| status | string | Registrant's status. * `approved` - Registrant has been approved. * `pending` - Registrant is in a pending list waiting for host or cohost approval. * `rejected` - Registrant has been rejected by the |
| orderType | string | Sort order for the registrants. |
| orderBy | string | Registrant ordering field. Ordered by `registrationTime` by default. * `firstName` - Registrant's first name. * `lastName` - Registrant's last name. * `status` - Registrant's status. * `email` - regis |
| emails | array | List of registrant email addresses. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/queryRegistrants",
"title": "queryRegistrants",
"type": "object",
"required": [
"emails"
],
"properties": {
"status": {
"type": "string",
"enum": [
"approved",
"pending",
"rejected"
],
"description": "Registrant's status.\n * `approved` - Registrant has been approved.\n * `pending` - Registrant is in a pending list waiting for host or cohost approval.\n * `rejected` - Registrant has been rejected by the host or cohost.\n"
},
"orderType": {
"type": "string",
"enum": [
"DESC",
"ASC"
],
"description": "Sort order for the registrants."
},
"orderBy": {
"type": "string",
"enum": [
"firstName",
"lastName",
"status",
"email"
],
"description": "Registrant ordering field. Ordered by `registrationTime` by default.\n * `firstName` - Registrant's first name.\n * `lastName` - Registrant's last name.\n * `status` - Registrant's status.\n * `email` - registrant's email.\n"
},
"emails": {
"type": "array",
"items": {
"type": "string",
"example": "bob@example.com"
},
"description": "List of registrant email addresses."
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/webex-queryregistrants"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.