Skip to content


Enboarder on Hire2Retire uses OAuth Client Credentials.

The Client Credentials Flow involves an application exchanging its application credentials, such as client ID and client secret, for an access token.

Please refer to the document OAuth Client Credentials for rest APIs to know more about authentication in Enboarder.

We at RoboMQ pay utmost attention to keep your account secure. See our Security and Privacy Policies to learn more about how RoboMQ handles your account access.

Object Permission
User Can Provision and Deprovision Users

Generate Client Credentials in Enboarder

To enable this in the account, an admin needs to enable it from Settings > Integration > Our Extensions.

Enboarder SCIM Endpoint and SCIM Bearer Token

Figure 1. Activate OAuth in Enboarder

Please click on the Activate OAuth2 button to generate Client ID and Secret for OAuth2 App client. Optionally the user can enable / disable OAuth2 setting from this page.

Enboarder SCIM Endpoint and SCIM Bearer Token

Figure 2. Client Id and Client Secret in Enboarder

To establish a connection to the Enboarder on Hire2Retire Provisioning, you need to provide the following OAuth information:

  • Instance URL - Your instance url is your base url for API requests.

  • Client Id - The client ID is a unique identifier assigned to your OAuth app in Enboarder platform.

  • Client Secret - The client secret is a confidential and unique identifier associated with your OAuth application in Enboarder platform.

  • Scope - Scope of your API.

Please visit Enboarder Documentation for more information.

Enboarder Bearer Token

Figure 3. Authentication Form for Enboarder OAuth Client Credentials on RoboMQ Hire2Retire