---
sourceDocument: Australia Conversational Interfaces
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/conversational-interfaces

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Configure multiple provider applications

# Configure multiple provider applications {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

You can configure multiple provider applications to support AI agents where there are multiple primary bots using Virtual Agent API and you need to distinguish between them.

## Vorbereitungen

Role required: admin

Be sure you are in Virtual Agent API application scope.

## Prozedur

1. Navigate to Allsys_cs_provider_application.
2. Click New to create a new provider application.
3. On the form, fill in the fields.  
   {#configure-multiple-provider-applications__table_ujp_1dp_kqb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the provider application, such as <kbd class="ph userinput">VA API Custom Bot</kbd>. |
   | Provider | Select the provider as VA Bot to Bot Provider. |
   | Inbound Id | Unique inbound Id used in the request message, for example, custom_1. |
   | Message Auth | Configure Message Authentication with a token for inbound communication. See [Configure Message Authentication for inbound communication](https://servicenow-prod.fluidtopics.net/Lh4HAjt_3MNwNsSdAWJsAQ "You can configure Message Authentication for the Virtual Agent API instead of Basic or OAuth. Message Authentication involves configuring either Static or Hash tokens, setting up Provider Authentication, and setting the channel identity.") for more details. |
   [ ]

   {#configure-multiple-provider-applications__table_ujp_1dp_kqb}
4. Click Submit.
5. Navigate to AllSystem Web ServicesREST Message.
6. Click New to create a new REST Message record.
7. In the REST Message record, fill in the form fields.  
   {#configure-multiple-provider-applications__table_fhw_fy3_n1c__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the REST Message record. This should be the same as the newly created provider application. |
   | Endpoint | The response endpoint of the primary bot. |
   [ ]

   {#configure-multiple-provider-applications__table_fhw_fy3_n1c}
8. Click Submit.
9. In the HTTP Methods section, click New to create a new method or you can override the default GET method.  
   {#configure-multiple-provider-applications__table_lfp_hcj_n1c__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the HTTP Method. Enter <kbd class="ph userinput">postMessage</kbd>. |
   | HTTP method | Select POST. |
   | Endpoint | Enter the response endpoint of the primary bot. |
   | Authentication Type | Configure Basic or OAuth 2.0 authentication as per your requirement. For details about configuring basic authentication, see [Configure a REST message with basic auth](https://www.servicenow.com/docs/access?context=t_ConfigureRESTMsgBasicAuth&version=australia&pubname=australia-api-reference&ft:locale=en-US). For information about configuring OAuth 2.0, see [Configure a REST message with OAuth](https://www.servicenow.com/docs/access?context=t_ConfigureARESTMessageWithOAuth&version=australia&pubname=australia-api-reference&ft:locale=en-US). |
   [ ]

   {#configure-multiple-provider-applications__table_lfp_hcj_n1c}
10. To use the newly created provider application, pass the Inbound Id of the provider application in the appInboundId parameter of the Virtual Agent API request.  
    You need to pass the Inbound Id of the provider application in the appInboundId parameter for every Virtual Agent API request. The following is a sample Virtual Agent API request that uses the newly created provider application.


        {
            "userId": "adminuser1",
            "emailId": "admin@example.com",
            "action": "START_CONVERSATION",
            "message": {
                "text": "",
                "typed": true
            },
            "appInboundId": "custom_1",
            "contextVariables": {
                "app_name": "test"
            }
        }

    You can test the configuration by viewing the outbound HTTP logs to verify that your response endpoint was called.