Bjorn Lunden
Configure and test a Bjorn Lunden connection with API.1.
Bjorn Lunden provides accounting, invoicing, payroll, and tax products for small and medium-sized businesses. Set up new Bjorn Lunden integrations with a System Setting in the Zwapgrid Client Portal.
Client Portal configuration
Available
Test option
Sandbox supplied with the vendor integration
Vendor documentation
Before you start
You need a Bjorn Lunden integration with an App Client ID, App Client Secret, and access to a sandbox company. Request access through the developer onboarding page.
List every API.1 and Proxy.1 operation your product will use before requesting permissions.
Confirm vendor permissions
Bjorn Lunden manages permissions for your application. They are not selected in the Zwapgrid System Setting.
Contact Bjorn Lunden API support with your application name, client ID, and the complete list of methods and endpoints you require. Include Proxy.1 calls in that list. Never include the client secret.
Changing application credentials does not copy permissions from the previous application. Ask Bjorn Lunden whether already connected companies must reactivate the integration after a change.
Configure Zwapgrid
In the Client Portal, open Systems → Bjorn Lunden → Configure.
Create a clearly named System Setting.
Enter the App Client ID and App Client Secret supplied for your integration.
Save and review the Draft.
Publish the setting when vendor permissions have been confirmed.
See System Settings for lifecycle and Consent-selection rules.
Test the connection
Add representative data to the sandbox company.
Create a Development Consent using the published setting.
Complete the Onboarding Flow.
Test every required read and write operation.
For a credential migration, validate one production company before moving the remaining connections.
Troubleshooting
Out of allowed scope: Ask Bjorn Lunden to review the application and the full endpoint list together.
403 Operation is forbiddenwithout details: Contact Zwapgrid support with the Consent ID, UTC timestamp, and correlation or request ID.
Never send client secrets, API keys, or access tokens in a support message.
Last updated
Was this helpful?
