How to Authenticate

This guide walks you through the complete process of setting up an ADP Workforce Now connector, including creating the required ADP project, generating the client ID and secret, requesting a certificate, configuring the necessary permissions, and establishing the connection.

Step 1: Open the magic link provided. This will lead to a linking page.

Step 2: Click on Allow and Continue.

The next screen will ask you for an ADP Client ID and Client Secret. You need to create these in ADP API Central.

Step 3: Sign in to ADP API Central, then select Create a Project.

Step 4: Enter a name and description that clearly identify the integration, then select Next.

Step 5: Select the use case that matches your integration requirements, then select Create Project.

Step 6: Once the project is created, select View Project.

Step 7: Scroll down, copy the client ID, and paste it in the Magic Link prompt.

Step 8: Click on Show Secret to reveal the client secret. Copy and paste it in the prompt.

Step 9: Click on Next to proceed.

Step 10: You will now be prompted to enter the ADP certificate details. To obtain these, return to API Central.

Step 11: Navigate to the certificate section and click on Request Certificate.

Step 12: Enter the required details and click on Next to proceed to generate a Private Key.

Step 13: Copy the entire private key and paste the copied key in the prompt on the linking page. Also store the private key securely on your local machine.

Step 14: Click on Next.

Step 15: Click on Done once the certificate starts being generated.

Step 16: Click on View to open the certificate. Copy the certificate and paste it into the provided prompt. Download a copy and store it securely for future reference.

Leave this page open without refreshing it, and proceed directly to the next step to configure the required permissions.

Step 17: Navigate to ADP Workforce Now and log in. Admin access is required for this step.

Step 18: Go to the Setup section and click on Access Permissions.

Step 19: Navigate to Manage Profiles and find the profile created for your API Central project.

Step 20: Go to Menus & Features and assign appropriate permissions. Clear any permissions that are not required.

Step 21: If the integration needs sensitive fields such as bank details, date of birth, Tax ID, deductions, accumulators, or compensation rates, open Sensitive Personal Information and configure the masking permissions.

Use the following settings for data that needs to be available to the integration:

Only unmask data that your integration actually requires.

Select Save after completing the permission setup.

Step 22: Click on Connect. The connection should now be established.

If you receive the following error:

This usually indicates that the required API access has not been added to the API Central project.

Please follow the steps below to verify and enable the required API access:

Once this is done, try connecting again using the magic link.

Yes. You can add missing permissions or API scopes even after the connection has been set up.

Once the permissions are updated for your ADP project, the newly accessible data will be reflected after the connector’s next sync. If needed, a manual sync can also be triggered to refresh the data sooner.

No API key is used in this setup. The Bindbee connection uses credentials generated through your ADP API Central project, including the Client ID, Client Secret, Private Key, and Certificate.

Open the project in ADP API Central. The Client ID is shown in the project's credentials section. Select Show Secret to reveal the Client Secret.

Yes. You need sufficient access to manage the project in ADP API Central and to configure Access Permissions in ADP Workforce Now.

Authentication and data access are separate. The API Central project determines which APIs are available, while the Workforce Now integration profile determines which data the integration can access. Sensitive-field masking can further restrict individual fields.

The exact scope depends on the data being synced. For employee data in this setup, confirm that the project includes the required v2/workers API access. If Bindbee reports a scope or permission error for another ADP resource, the corresponding API may also need to be added to the project.