Required Scopes and Endpoint Domains for ServiceNow

When integrating with ServiceNow, your application needs specific permissions to interact with the API.

These permissions are defined by access scopes, which determine what data your application can access and what actions it can perform.

This topic provides information about the required access scopes and endpoint domains for the ServiceNow connector.

Understanding Scopes

Scopes are a way to limit an application's access to a user's data. They define the specific actions that an application can perform on behalf of the user.

For example, a read-only scope might allow an application to view data, while a full access scope might allow it to modify data.

Required Scopes for ServiceNow

Scope	Description
useraccount	This scope grants access to the user’s account information and preferences. This is the default scope and the only scope available.

Understanding Endpoint Domains

Endpoint domains are the specific URLs that the application needs to communicate with in order to authenticate, retrieve records, and perform other essential operations.

Allowlisting these domains ensures that the network traffic between your application and the API is not blocked by firewalls or security settings.

Note: Most users do not need to make any special configurations. Allowlisting is typically only necessary for environments with strict security measures, such as restricted outbound network traffic.

Required Endpoint Domains for ServiceNow

Domain	Always Required	Description
<URL>	TRUE	The URL of your ServiceNow instance as provided in the Url connection property.
<SSOLoginURL>	FALSE	The URL of your SSO provider. Required when AuthScheme is set to OKTA, ADFS, or PingFederate.
<Subdomain>.onelogin.com	FALSE	The subdomain of the OneLogin user accessing the SSO application. Required when AuthScheme is set to OneLogin and you have set a subdomain in SSOProperties.
<RelyingParty>	FALSE	The identifier of your ADFS relying party. Required when AuthScheme is set to ADFS and you have set a relying party in SSOProperties.