Bigquery + Svea

Integration documentation and guides

Getting Started · 2

Getting Started

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

oauth2 · Until access is revoked, disconnected, or re-authentication is required

3 minutes

1
Open the BigQuery connector in Junipeer
Start the BigQuery connection from the relevant connector or onboarding step in Junipeer.
2
Click Connect
Use the connect action in Junipeer to start the Google sign-in flow.
3
Sign in with the correct Google account
Choose the Google account that has access to the BigQuery project and dataset you want Junipeer to use.
4
Review and approve access
Google shows the requested access before you approve the connection. Review the consent screen and continue only if the account and permissions are correct.
5
Confirm the target project or dataset if prompted
If Junipeer asks you to choose a project, dataset, or similar target, pick the one that should be connected.
6
Return to Junipeer and verify the connection
After consent is approved, return to Junipeer and make sure the connector shows as connected.

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.