Using Virtual Agent API
Summarize
Summary of Using Virtual Agent API
The ServiceNow® Virtual Agent API app enables integration of any chat interface or bot with ServiceNow Virtual Agent or Agent Chat via a REST API. Available from the ServiceNow Store, this API supports both standalone bot deployments and multi-bot environments where Virtual Agent acts as a secondary bot managed by a primary bot such as IBM Watson Assistant or Microsoft LUIS. It also supports Bot Interconnect for unified chat experiences across multiple channels and enterprise tasks.
Show less
This API is designed for server-to-server integrations, allowing end users to interact with Virtual Agent through various chat platforms. For chat interfaces requiring transformation of unsupported controls, the Custom Chat Integration Framework is recommended.
How It Works
- User input is submitted via a third-party chat interface or primary bot.
- The input is sent as a POST request in JSON format to the Virtual Agent API inbound REST endpoint.
- ServiceNow’s AI Platform authenticates and processes the request, routing it to Virtual Agent or a live agent.
- A POST response JSON with the bot’s reply is sent back through the outbound REST endpoint.
- The primary bot or chat interface displays the response to the user.
Key Features
- Supports rich control features and notifications consistent with Virtual Agent and Agent Chat.
- Version 3.0.x adds file upload from private URLs and synchronous handshake improvements.
- Enables bot-to-bot communication in multi-bot environments with automatic closure of idle conversations.
- Supports configuration of multiple provider applications to differentiate AI agents in complex integrations.
- Includes scripted extension points for transforming API requests and responses into supported formats.
- Enables Now Assist experience to support generative AI skills across multiple provider channels.
Installation and Configuration
- Install the Virtual Agent API app from the ServiceNow Store.
- Review and configure the Scripted REST API inbound endpoint and set up authentication (Basic, OAuth, or Message Authentication with Static/Hash tokens).
- Configure the outbound REST endpoint URL and authentication to receive responses from Virtual Agent.
- Set up provider applications for managing multiple primary bots if applicable.
Limitations and Compatibility
- The API does not support chat branding via this integration.
- Requires a Pro license similar to Virtual Agent.
- Compatibility varies by version, supporting releases from Paris through Washington DC, with some features limited in Quebec.
Practical Benefits for ServiceNow Customers
By using the Virtual Agent API, customers can seamlessly integrate ServiceNow Virtual Agent capabilities into their existing chat platforms or bots, extending conversational support across multiple channels. This enables automation of service requests, ticketing, and other enterprise tasks directly within familiar chat environments, improving user engagement and operational efficiency. The API’s support for complex multi-bot scenarios and advanced authentication options ensures secure, scalable, and flexible deployments tailored to enterprise needs.
Use the ServiceNow® Virtual Agent API app to integrate any chat interface or a bot with ServiceNow® Virtual Agent or Agent Chat. The app is available from the ServiceNow® Store.
Overview of the Virtual Agent API
The Virtual Agent API is a REST API. This API is built on the conversational custom chat integration framework that is provided with Virtual Agent starting in the Paris release. The API enables ServiceNow developers, advanced users, and admins to use Virtual Agent in either of the following ways:
- Standalone bot
- Use Virtual Agent as a standalone bot that you integrate with
enterprise or with any other third-party chat interface that supports conversational
interfaces.
Your end users can interact with the Virtual Agent and Agent Chat through multiple channels by using this integration.
- Secondary bot
- Use Virtual Agent as a secondary bot in an environment that has multiple, specialized bots managed by a primary bot.
In this scenario, a primary bot manages communication with secondary bots on behalf of the end user. A primary bot could be IBM Watson Assistant, Microsoft LUIS, or a homegrown primary bot.
Your secondary bots, such as the ServiceNow bot, might handle specific types of end-user requests, such as service tickets or reservations.
- Bot Interconnect
- Use Virtual Agent Bot Interconnect as the primary bot in a diverse chat environment. Bot Interconnect creates a unified chat experience and gives your end users access to multiple channels and a wide variety of enterprise tasks that are available from ServiceNow.
The Virtual Agent API is useful for creating server-to-server integrations. However, for integrations that require the transformation of unsupported controls that must be rendered in your existing chat interface, consider using the Custom Chat Integration Framework.
For information about features such as the URL format and the supported request and response parameters in the Virtual Agent API, see Virtual Agent Bot Integration API.
Augment your experiences with the Virtual Agent API (Virtual Agent Academy video)
How the Virtual Agent API works
- The user provides input to a primary bot or third-party chat interface.
- The bot sends a POST request JSON to the inbound REST endpoint (via scripted REST API).
- The ServiceNow AI Platform authenticates and processes the request, which is sent to Virtual Agent or a live agent.
- The ServiceNow AI Platform sends a POST response JSON from the outbound REST endpoint (via REST API) back to the bot.
- The primary bot or third-party chat interfaces displays the response to the user.
To see a demonstration of the Virtual Agent API and an FAQ, see Getting Started with Virtual Agent APIs on the Community site.
Limitations
- Chat branding through this Virtual Agent API integration
Version and release compatibility
| Version | Compatible Releases |
|---|---|
| 3.10.0 | Washington DC |
| 3.9.x | Vancouver |
| 3.8.x | Vancouver |
| 3.7.x | Utah |
| 3.5.x | Tokyo |
| 3.0.x | San Diego |
| 2.0.x | Rome
A subset of features is compatible with Quebec. |
| 1.3.0 | Quebec |
| 1.0.12 | Quebec |
| 1.0.9 | Paris |