A municipal NOC ChatOps bot posts outage notices into a Webex ops space around the clock. Which credential should the service present on each Webex API call?
Select an answer to reveal the explanation.
Short Explanation
Think of the bot token as the building’s badge for a dedicated robot account—always on duty, never pretending to be a person. A personal portal token is a short-lived visitor pass, and three-legged OAuth is how an integration borrows a user’s identity, not the default ChatOps bot pattern.
Full Explanation
Webex ChatOps services that post and receive in an ops space authenticate with the bot’s access token as Authorization: Bearer. Personal developer-portal tokens expire in hours and represent a person, so they are a poor production credential. Three-legged OAuth (authorization-code grant) is how an integration obtains a user token; it is not the default unattended ChatOps bot pattern. Cross-platform keys such as Meraki Dashboard headers do not authenticate the Webex API.