A Python CLI that uses wxc_sdk and documented Webex Calling APIs to read and toggle call intercept (on/off) for a user identified by email.
Why use this playbook
- Ship faster: Start from a working People lookup plus person_settings.call_intercept flow instead of reverse-engineering payloads from scratch.
- Flexible auth: Supports a passed-in token, WEBEX_ACCESS_TOKEN, or OAuth via integration credentials loaded from the environment.
- Secrets-safe pattern: Integration IDs, secrets, and tokens are intended for environment variables (see env.template), not hardcoded values.
- Easy to verify: Single-user CLI with optional debug logging for REST traces during development.
What it does
- Resolves person_id by listing People with the target email.
- Calls person_settings.call_intercept.read to print whether intercept is on or off.
- Optionally calls person_settings.call_intercept.configure when you pass on or off, then re-reads to confirm the new state.
- Can obtain tokens through a local OAuth redirect to localhost:6001 and cache them in a YAML file next to the script.
Preview listing
This App Hub entry was published from an open pull request. Review the change.
Support
Third-Party Tool
—
Estimated Implementation Time
1-2 hours
Categories
A Python CLI that uses wxc_sdk and documented Webex Calling APIs to read and toggle call intercept (on/off) for a user identified by email.
Why use this playbook
- Ship faster: Start from a working People lookup plus person_settings.call_intercept flow instead of reverse-engineering payloads from scratch.
- Flexible auth: Supports a passed-in token, WEBEX_ACCESS_TOKEN, or OAuth via integration credentials loaded from the environment.
- Secrets-safe pattern: Integration IDs, secrets, and tokens are intended for environment variables (see env.template), not hardcoded values.
- Easy to verify: Single-user CLI with optional debug logging for REST traces during development.
What it does
- Resolves person_id by listing People with the target email.
- Calls person_settings.call_intercept.read to print whether intercept is on or off.
- Optionally calls person_settings.call_intercept.configure when you pass on or off, then re-reads to confirm the new state.
- Can obtain tokens through a local OAuth redirect to localhost:6001 and cache them in a YAML file next to the script.
Preview listing
This App Hub entry was published from an open pull request. Review the change.