Skip to main content
You will need a ServiceNow account with admin privileges (or equivalent roles that can manage API Access Policies). Basic Auth must be allowed in two places: (1) a REST API Access Policy covering the Table API, and (2) the BasicAuth inbound authentication profile must be Active.

​
Before you begin

Make sure you have access to a ServiceNow instance before starting.

1

Check prerequisites

You need an existing ServiceNow instance and an account with sufficient permissions.

  • An active ServiceNow instance. If you do not have one, request a free Personal Developer Instance from the ServiceNow Developer Program or contact your ServiceNow administrator for access.
  • An account with the admin role (or roles that can manage REST API Access Policies and Inbound Authentication Profile records).
  • Your instance URL, in the format https://{your-instance}.service-now.com (for example, https://dev12345.service-now.com).

​
Configure the REST API Access Policy

ServiceNow gates access to the Table API behind REST API Access Policies. You need a policy covering the Table API that allows Basic Authentication.

1

Sign in to your ServiceNow instance

Open your instance URL and log in.

  • Go to https://{your-instance}.service-now.com
  • Enter your User name and Password, then click Log in
ServiceNow login page with the Log in button highlighted
2

Open REST API Access Policies

Click All in the top navigation bar, then type rest api access in the Filter box. Click REST API Access Policies under System Web Services > API Access Policies.

All menu filtered to show the REST API Access Policies module
3

Identify the Table API policy

In the API Access Policies list, look for the policy that covers the Table API. Policy names vary by ServiceNow release and instance — identify it by its columns, not its name: REST API = Table API and REST API PATH = now/table.

  • Depending on your ServiceNow release and instance configuration, this may be a single Table API policy or separate Table GET API Access Policy and Table POST API Access Policy records
  • If a Table API policy exists, continue to the next step to verify it
  • If no Table API policy exists, skip ahead to the step for creating a new policy
API Access Policies list with the Table API policy row highlighted
4

Verify the policy is Active

Open the Table API policy record and confirm Active is checked. Also confirm the coverage checkboxes are ticked - Apply to all methods, Apply to all resources, Apply to all versions, and Apply to all tables.

Table API access policy record with the Active checkbox highlighted
5

Confirm the policy allows Basic Auth

On the same policy record, Basic Auth is allowed if either of the following is true. Click Update if you changed anything.

  • Advertise all auth schemes is checked, or
  • BasicAuth for none public processors appears in the Inbound authentication profiles related list. To add it, click Insert a new row…, pick BasicAuth for none public processors, then click Update
Inbound authentication profiles related list on the policy showing BasicAuth for none public processors
6

Create a new policy only if none exists

If the list has no Table API policy at all, click New and fill in the form.

  • Name: enter a descriptive name (for example, StackOne Connector Policy)
  • Active: leave checked
  • Global: leave unchecked unless the policy should apply across all application scopes
  • REST API: select Table API (REST API PATH auto-fills to now/table)
  • Apply to all methods, Apply to all resources, Apply to all versions, Apply to all tables: check all four
  • Advertise all auth schemes: check it to allow Basic Auth alongside any explicit profiles, or leave it unchecked and add BasicAuth for none public processors under Inbound authentication profiles via Insert a new row…
  • Click Submit
New API Access Policy form with REST API set to Table API

​
Activate the BasicAuth Inbound Authentication Profile

ServiceNow ships a built-in inbound authentication profile named BasicAuth for none public processors that handles Basic Auth across all non-public REST endpoints. If it is inactive, every Basic Auth request returns HTTP 401 even with valid credentials.

1

Open Inbound Authentication Profile

Click All in the top navigation bar, type inbound auth in the Filter box, then click Inbound Authentication Profile under System Web Services > API Access Policies.

All menu filtered to show the Inbound Authentication Profile module
2

Find the BasicAuth profile

In the Authentication Profiles list, look for the row named BasicAuth for none public processors (its Apply to all none public processors column reads true).

Authentication Profiles list with BasicAuth for none public processors highlighted
3

Verify the profile is Active

Open the record. If Active is unchecked, check it and click Update. The Type field reads Basic Auth. Because Apply to all none public processors is true, no further wiring is required.

BasicAuth for none public processors record with the Active checkbox highlighted
4

Create the profile only if missing

On hardened instances the profile may have been removed. From the Authentication Profiles list, click New. When the form asks What kind of authentication profile?, select Create standard http authentication profiles.

  • Name: enter a descriptive name (for example, BasicAuth for none public processors)
  • Active: check it
  • Apply to all none public processors: check it
  • Click Submit
What kind of authentication profile page with Create standard http authentication profiles highlighted

​
Enter your credentials in StackOne

Collect the three values below and enter them in StackOne Hub.

1

Fill in the connection fields

Each field in StackOne Hub maps to your ServiceNow account details.

  • Instance Name — the subdomain of your ServiceNow URL, without .service-now.com. Format: {your-instance}. Example: dev12345 (from https://dev12345.service-now.com)
  • Username — the User name you use to sign in to ServiceNow
  • Password — the Password for that account
  • Native Webhook URL — read-only; StackOne fills this automatically for webhook events, no action needed
  • The account must have roles that grant Table API access (such as admin or itil)

​
Linking the Account from the Hub

1

Navigate to the Hub

Use one of the three Linking Account Methods to access the Hub.
2

Fill out the fields

Fill out the following fields using details from your provider:
  • Instance Name
  • Username
  • Password
3

Connect

  • Click Connect
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup

If the account linking is successful, you will see the newly linked account in your Accounts page.

​
Next Steps

Webhooks setup

Configure receiving Events for ServiceNow into StackOne.