Brightpearl + Svea

Integration documentation and guides

Getting Started · 2

Getting Started

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

oauth2 · The client credentials stay valid until rotated or revoked. OAuth access tokens are short-lived and generated from these credentials.

10-15 minutes

1
Confirm the Brightpearl account context
Identify the correct Brightpearl account code and environment before starting authorization.
2
Use the agreed Brightpearl app setup
Have Junipeer or the app owner confirm the Brightpearl app/client that should be used for the integration.
3
Authorize the integration
Complete the Brightpearl authorization flow for the correct merchant account and environment.
4
Save the account-specific identifiers
Keep any Brightpearl account code, app reference, or related identifiers required by the integration.
5
Finish the setup in Junipeer
Enter the agreed Brightpearl values in Junipeer and verify the connection.

token · The merchant credentials stay valid until changed or revoked. Authentication tokens are generated from these credentials per request.

10 minutes

1
Contact Svea to get started
Start with your Svea sales or onboarding contact to set up the merchant account and test environment.
2
Get the test credentials
Ask Svea for the CheckoutMerchantId and CheckoutSecret for the test environment first.
3
Store the values securely
Save both the merchant ID and the secret securely because they are both required to build the authentication token.
4
Paste the values into Junipeer
Enter the CheckoutMerchantId and CheckoutSecret in Junipeer.
5
Repeat for live when you are ready
Before go-live, request and use the live credentials for the production environment if they differ from the test setup.