Business Central + nShift

Open the Business Central connector in Junipeer

Start the Business Central connection from the relevant connector or onboarding step in Junipeer.

Click Connect

Use the connect action in Junipeer to start the Microsoft sign-in flow.

Sign in with the right Microsoft account

Choose the Microsoft 365 or Microsoft Entra account that has access to the Business Central environment Junipeer should connect to.

Review and approve the OAuth consent

Microsoft shows the requested permissions before you approve the connection. Continue only if the tenant and account are correct.

Confirm environment or company if needed

If Junipeer asks you to choose an environment or company, select the one that should be connected.

Return to Junipeer and verify the connection

After the approval flow completes, go back to Junipeer and make sure the Business Central connector is connected.

Log in to nShift Delivery

Open nShift Delivery and sign in with the account that should manage the API key.

Open API keys

Go to Maintenance → API keys.

Create a new key

Click New API key, keep Status as Enabled, and set Type to Web Services (REST).

Enter the key details

Add a Note, optionally restrict valid IP addresses, enter the correct Developer ID, and choose a Profile if the key should be profile-specific.

Save and copy the generated values

When you save, nShift generates an ID, a Secret ID, and a combined ID. Use the ID and Secret ID to authenticate against the REST API framework.

Paste the credentials into Junipeer

Enter the API key ID, Secret ID, and Developer ID in Junipeer if those fields are requested by the connection setup.