Authenticating ServiceNow CPQ API calls

Secure ServiceNow CPQ API calls with admin API keys, JWT tokens, session cookies, or Google IdP for runtime and Admin tasks.

Authenticating runtime API calls

When using ServiceNow CPQ in a headless manner, you authenticate your configuration session by using a runtime client. To create a runtime client, navigate to the ServiceNow CPQ Admin UI, click Utilities in the sidebar, and then click Runtime Clients. From here, specify the origin of your call, whether it is an external URL or an origin specified in the header of your call. You can also give your client an expiration date. After you save your client, you can copy the token and use it as the bearer token in other runtime API calls.

For more information on ServiceNow CPQ runtime calls, see Intro to runtime API calls.

Authenticating admin API calls

There are four ways to authenticate your admin API calls:

• Admin API keys

  Admin API keys are the recommended way of authenticating admin API calls. For information about setting up admin API Keys, see:

  ServiceNow CPQ: admin API Keys.

• JWT token

  To ensure tighter security for long-term admin API authentication, we leverage the Salesforce JWT web token. For steps to initialize this access flow, see:

  Admin APIs: Authentication using a Salesforce-connected app

• Session cookies

  To authenticate a short term admin session, you can leverage your browser’s session cookie. Navigate to the cookies in your browser’s console, and take the session cookie. Enter the cookie in your request header as a keyed pair: "Cookie”:”SESSION=<yourSessionCookie>"

• Google IdP

  If you are not connected to a Salesforce environment and choose not to use admin API keys, you can use Google IdP to authenticate. If you do not use Google IdP, open a support case to discuss options for admin API authentication.

  Note: Create a support case by using the ServiceNow Support portal. For step-by-step instructions, see Create a case on Now Support for CPQ Customers.