Brink + nShift

Integration documentation and guides

Getting Started · 2

Getting Started

Start with credentials, setup steps, and the key guides for this pair.

token · Varies by agreed setup

Varies by project

1
Confirm the exact product and environment
Verify the product variant, environment, tenant, and any middleware involved before configuring credentials.
2
Let Junipeer confirm the auth pattern
Use the agreed Junipeer implementation scope to confirm whether the setup uses API keys, service users, OAuth, tokens, or another method.
3
Create or receive the technical credentials
Have the system owner, vendor, or implementation partner create the required integration access according to the agreed setup.
4
Add the credentials in Junipeer
Enter the issued credentials, host details, and any tenant-specific identifiers in the Junipeer admin when requested.
5
Verify in a non-production environment first
Run a controlled connection test before enabling a live data flow.

basic_auth · Until disabled, replaced, or deleted

10 minutes

1
Log in to nShift Delivery
Open nShift Delivery and sign in with the account that should manage the API key.
2
Open API keys
Go to Maintenance → API keys.
3
Create a new key
Click New API key, keep Status as Enabled, and set Type to Web Services (REST).
4
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.
5
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.
6
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.