---
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 Protect API

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

Release version: Australia  
Updated April 29, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configures the 3E Credentials record and obtains the OAuth access token required to authenticate with the 3E Protect API.

## Before you begin

Role required: admin

## About this task

The 3E Protect integration uses OAuth 2.0 client credentials to authenticate with the 3E API. The 3E Credentials record references an OAuth Entity Profile that stores the client ID and secret from your 3E subscription. An
OAuth access token must be obtained and validated before SDS retrieval and chemical data requests can function. If the token expires before an automatic refresh occurs, a banner notification on the credential record prompts
you to request a new one. For more information on configuring 3E Protect application registry, [Configure the application registry for the 3E service provider](https://servicenow-prod.fluidtopics.net/EGdiCr69X7SLL3c_pnxzcQ "Configure 3E integration with Health and Safety Environmental Management to retrieve current chemical data.").

## Procedure

1. Navigate to AllIntegrationHubConnections and Credential Aliases.
2. Open the 3E Credentials \[sn_hs_spoke_3e.3E_Credentials\] record.
3. In the Credentials column, open the 3E 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 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 record and triggering an sync request. For more information, see [Sync chemical information with the 3E database](https://servicenow-prod.fluidtopics.net/9BeDBLmB86NsZx4ZKx1Nsw "You can sync details of chemicals, such as hazard identification, chemical ingredients, and others, with the 3E database to ensure that current information is accessible.").
* A successful request populates the chemical record with hazard identification, ingredient data, and SDS documents retrieved from the 3E server. If the request fails, verify that the OAuth Entity Profile is configured correctly with valid 3E subscription credentials.

*[\>]: and then