Reference
Webex
Set up Webex OAuth for team messaging, video meetings, and collaboration
Overview
Section titled “Overview”Connect your users to Webex for team messaging, video conferencing, room management, and collaboration integrations.
| Property | Value |
|---|---|
| Provider ID | webex |
| Category | Communication |
| PKCE | Supported |
| Token refresh | Automatic |
| Redirect URI | Shown in Developer Portal |
Step 1: Create a Webex OAuth App
Section titled “Step 1: Create a Webex OAuth App”Go to the Webex Developer Portal
Navigate to developer.webex.com/my-apps and sign in.
Create a new integration
Click Create a New App > Create an Integration. Fill in the integration name, description, and icon.
Configure the redirect URI
Add the Alter callback URL from the Developer Portal to the Redirect URI(s) field.
Get credentials
Copy the Client ID and Client Secret.
Step 2: Add to Alter Vault
Section titled “Step 2: Add to Alter Vault”Open the Developer Portal
Go to portal.alterauth.com and navigate to the application.
Add Webex provider
Go to OAuth Providers > Add Provider > Webex.
Enter credentials
- Client ID: Paste your Webex Client ID
- Client Secret: Paste your Webex Client Secret
Select scopes
Choose the scopes the application needs.
Save
Click Save. The provider is now active.
Available Scopes
Section titled “Available Scopes”| Scope | Description |
|---|---|
spark:all | Full access to all Webex resources |
spark:people_read | Read user profiles and directory information |
spark:rooms_read | Read Webex rooms and spaces |
spark:messages_read | Read messages in Webex spaces |
spark:messages_write | Send messages to Webex spaces |
spark:memberships_read | Read space membership information |
meeting:schedules_read | Read meeting schedules and details |
meeting:schedules_write | Create and manage meeting schedules |
- For most integrations, using specific scopes rather than
spark:allis recommended. - See the Webex integrations documentation for more details.
Policy-cataloged operations
Section titled “Policy-cataloged operations”Alter policy rules can target these attested operations and families for operation-level and parameter-aware controls.
| Operation ID | Families | Method | Provider path |
|---|---|---|---|
meetings/create | write | POST | /v1/meetings |
meetings/delete | delete | DELETE | /v1/meetings/{meetingId} |
meetings/get | read | GET | /v1/meetings/{meetingId} |
meetings/list | read | GET | /v1/meetings |
memberships/create | admin | POST | /v1/memberships |
memberships/list | read | GET | /v1/memberships |
messages/create | send | POST | /v1/messages |
messages/delete | delete | DELETE | /v1/messages/{messageId} |
messages/get | read | GET | /v1/messages/{messageId} |
messages/list | read | GET | /v1/messages |
people/get | read | GET | /v1/people/{personId} |
people/list | read | GET | /v1/people |
people/me | read | GET | /v1/people/me |
recordings/list | read | GET | /v1/recordings |
rooms/create | write | POST | /v1/rooms |
rooms/delete | delete | DELETE | /v1/rooms/{roomId} |
rooms/get | read | GET | /v1/rooms/{roomId} |
rooms/list | read | GET | /v1/rooms |
rooms/update | write | PUT | /v1/rooms/{roomId} |
teams/create | write | POST | /v1/teams |
teams/list | read | GET | /v1/teams |
webhooks/create | admin | POST | /v1/webhooks |
webhooks/list | read | GET | /v1/webhooks |