---
title: "Configuring ServiceNow for Integration"
slug: "configuring-servicenow-for-integration"
updated: 2026-04-27T07:00:56Z
published: 2026-04-29T10:55:15Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.britive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring ServiceNow for Integration

Britive supports API key-based and basic authentication for ServiceNow integration. Britive supports two ticket categories for ServiceNow integration: Incidents and Change requests.

Before creating a ServiceNow connection in Britive, you must create a service account using the following steps based on the selected authentication method.

- For API key-based authentication:
  - [Create a service user account](/v1/docs/configuring-servicenow-for-integration#create-a-service-user-account)
  - [Create an API key](/v1/docs/configuring-servicenow-for-integration#create-an-api-key)
- For basic authentication:
  - [Create a service user account](/v1/docs/configuring-servicenow-for-integration#create-a-service-user-account)

Steps to be followed on the ServiceNow instance:

### Create a service user account

Create a ServiceNow user using the following steps:

1. Create a user with a valid email address and password. For more information, see [Users and Groups](https://developer.servicenow.com/dev.do#!/learn/courses/rome/app_store_learnv2_aescreateappfromscratch_rome_create_an_app_from_scratch_with_app_engine_studio/app_store_learnv2_aescreateappfromscratch_rome_secure_apps_and_data/app_store_learnv2_aescreateappfromscratch_rome_users_and_groups) ServiceNow documentation.
2. Assign *sn_incident_read* and *sn_change_read* roles to the created user. For more information, see [Assigning a Role to a User](https://developer.servicenow.com/dev.do#!/learn/courses/rome/app_store_learnv2_securingapps_rome_securing_applications/app_store_learnv2_securingapps_rome_securing_applications_against_unauthorized_users/app_store_learnv2_securingapps_rome_roles).

### Create an API Key

Note:

Required only for API key-based authentication.

Create an API Key in the ServiceNow instance using the following steps:

1. Create an API key. For more information, see the [Configure API key](https://docs.servicenow.com/bundle/washingtondc-platform-security/page/integrate/authentication/task/configure-api-key.html) ServiceNow documentation. Enter the following fields while creating an API key.
  1. Select the default option *x-sn-apikey: Auth Header* for **Auth Parameter**.
  2. Associate the user created in [Creating a user account](/v1/docs/configuring-servicenow-for-integration#a-create-a-user-account) with the REST API key.
  3. Enter the following options in the **API Access Policies** form**.**For more information about ServiceNow access policies, see [REST API access policies](https://docs.servicenow.com/bundle/xanadu-platform-security/page/integrate/inbound-rest/concept/api-access-policy-prioritization.html).
    1. Enter the name of the API key.
    2. Check the **Active** checkbox.
    3. Select **Table API** from the **REST API** drop-down list.
    4. Check these checkboxes: **Apply to all methods**, **Apply to all resources**, **Apply to all versions**.
2. [Optional] The API key creation and defining access policy impact the REST API basic authentication. Add the **On-call subscription basic authentication profile** to the **Authentication Profile**for the above-created access policy to avoid impacting basic authentication. This additional step is required only if the ServiceNow instance is already using or planning to use basic authentication for other functions, including the ServiceNow onboarded application in Britive.

Note:

The ServiceNow onboarded application uses basic authentication. For more information, see the [ServiceNow Onboarding Guide](https://docs.britive.com/docs/britive-servicenow-integration-guide).

### Configuring ServiceNow setting for filter syntactical validation

The ServiceNow default behavior ignores the invalid part of the query. To alter this default behavior, you need to set *glide.invalid_query.returns_no_rows*property to *True.*This setting is required for syntactical validation of the *sysparm_query* parameter used in Britive. If this parameter is not configured, it is the administrator's responsibility to define the correct value for the *sysparm_query.*

For more information about the ServiceNow Table API and *sysparm_query* parameter, see [Table API](https://docs.servicenow.com/bundle/xanadu-api-reference/page/integrate/inbound-rest/concept/c_TableAPI.html).

Note:

The *glide.invalid_query.returns_no_rows* property controls the behavior of all queries across the ServiceNow instance, so make sure it does not disrupt other functions.

In the ServiceNow instance, navigate to **System Properties->Categories->Search**and select **System-> Properties New*******->*Add**the property with the name *glide.invalid_query.returns_no_rows*and *value*as *true.*