Properties
| Name | Type | Description |
|---|---|---|
| schemas | array | An array of schema URNs that define the structure of the SCIM resource. |
| userName | string | The unique identifier for the user. This must be set to the user's primary email address. The `userName` value must be unique across Webex and is used for authentication. |
| emails | array | A list of the user's email addresses. |
| name | object | |
| organization | string | The unique identifier for the organization. |
| id | string | The unique identifier for the user. |
| displayName | string | The display name of the user in Webex. |
| meta | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/ArchiveUser",
"title": "ArchiveUser",
"type": "object",
"required": [
"schemas",
"id",
"userName",
"emails",
"meta"
],
"properties": {
"schemas": {
"type": "array",
"items": {
"type": "string",
"example": "urn:scim:schemas:core:1.0,urn:scim:schemas:extension:cisco:commonidentity:1.0"
},
"description": "An array of schema URNs that define the structure of the SCIM resource."
},
"userName": {
"type": "string",
"example": "test_user2@example.com",
"description": "The unique identifier for the user. This must be set to the user's primary email address. The `userName` value must be unique across Webex and is used for authentication."
},
"emails": {
"type": "array",
"items": {
"$ref": "#/components/schemas/EmailObject"
},
"description": "A list of the user's email addresses."
},
"name": {
"$ref": "#/components/schemas/NameObject"
},
"organization": {
"type": "string",
"example": "410139c6-3bff-4404-9782-09a456ba2cae",
"description": "The unique identifier for the organization."
},
"id": {
"type": "string",
"example": "b96936c9-5b86-4a01-8969-e945c91b62f6",
"description": "The unique identifier for the user."
},
"displayName": {
"type": "string",
"example": "Mike Tang",
"description": "The display name of the user in Webex."
},
"meta": {
"$ref": "#/components/schemas/MetaObject"
}
}
}
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-archiveuser"
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.