---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/employee-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Configure OAuth authentication for the 3E Regulatory Intelligence API

# Configure OAuth authentication for the 3E Regulatory Intelligence API {#ariaid-title1}

Release version: Australia  
Updated April 29, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure the 3E Regulatory credentials alias with the Client ID and Client Secret required to authenticate with the 3E Regulatory Intelligence API.

## Before you begin

Role required: admin

## About this task

The 3E regulatory intelligence integration uses OAuth 2.0 client credentials to authenticate with the 3E API. The 3E Regulatory Credentials record references an OAuth entity profile that stores the Client ID and Client Secret from your 3E subscription. An OAuth access token must be obtained and validated before regulatory list retrieval can
function. If the token expires, a banner notification on the credential record prompts you to request a new one. For more information on connections, credentials, and aliases, see [Explore credentials, connections, and aliases](https://www.servicenow.com/docs/access?context=credentials-connections-alias&version=australia&pubname=australia-platform-security&ft:locale=en-US). For more information on configuring 3E regulatory application registry, see [Configure the application registry for 3E Regulatory Intelligence](https://servicenow-prod.fluidtopics.net/IoP2cX8gVZbg7xn5Yz_T~w "Configure 3E Regulatory Intelligence with Health and Safety Environmental Management to retrieve regulatory list data from 3E server and populate the Regulatory tab on chemical substance records.").

## Procedure

1. Navigate to AllIntegrationHubConnections and Credential Aliases.
2. Open the 3E Regulatory Credentials \[sn_hs_spoke_3e.3E_Credentials\] record.
3. In the Credentials column, open the 3E Regulatory Credentials record.
4. Verify that the OAuth Entity Profile field references the correct profile for your 3E Regulatory Intelligence subscription.
5. Under Related Links, select Get OAuth Token.  
   The system contacts the 3E authorization server using the Client ID and Client Secret stored in the OAuth Entity Profile and retrieves an access token. The token refreshes automatically on subsequent syncs.

## What to do next

* Verify the configuration by navigating to a chemical substance record and triggering a Sync regulatory list. For more information, see [Sync regulatory list regulations for a chemical substance](https://servicenow-prod.fluidtopics.net/JoO2PaE3vwpTu_AEpHJAaA "You can trigger a sync with the 3E Regulatory Intelligence server to retrieve all regulatory list data associated with a chemical substance based on its CAS (Chemical Abstracts Service) number.").
* A successful sync populates the Regulatory tab with regulations fetched from the 3E server. If the sync fails, verify that the OAuth Entity Profile is configured correctly with valid 3E subscription credentials.
{#hs-configure-3e-regulatory-intelligence-credentials__ul_ry3_xpb_cjc}

*[\>]: and then