Configure OAuth authentication for the 3E Regulatory Intelligence API

  • Release version: Australia
  • Updated April 29, 2026
  • 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. For more information on configuring 3E regulatory application registry, see Configure the application registry for 3E Regulatory Intelligence.

    Procedure

    1. Navigate to All > IntegrationHub > Connections 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.
    • 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.