Visma Spiris
Configure Visma Spiris credentials and scopes in Zwapgrid.
Visma Spiris, previously known as Visma eAccounting and Visma Spcs, provides bookkeeping, invoicing, and payroll products. Set up new Spiris integrations with a System Setting in the Zwapgrid Client Portal.
Client Portal configuration
Available
Test option
Spiris partner sandbox
Vendor documentation
Register for partner access
Register through the Spiris API sandbox form. Spiris supplies the application credentials and a sandbox company by email.
Use the sandbox only for application development. It cannot access production customers and some connected services are mocked or unavailable.
Choose permissions
List every API.1 and Proxy.1 operation your product will use. Select the minimum matching Spiris scopes, including the required API and offline-access scopes documented by Spiris.
Read the vendor's current authentication and scope reference before publishing your configuration.
Configure Zwapgrid
In the Client Portal, open Systems → Spiris → Configure.
Create a System Setting for the sandbox application.
Enter the Spiris Client ID and Client Secret.
Select the scopes required by your integration and confirm they match the vendor registration.
Save, review, and publish the setting.
See System Settings for lifecycle and Consent-selection rules.
Test and move to production
Create a Development Consent using the published sandbox setting.
Connect the sandbox company through the Onboarding Flow.
Test all required operations and retain any vendor error IDs for troubleshooting.
Contact Spiris API support when you are ready for production access.
Store production credentials in a separate Zwapgrid System Setting.
Never send the Spiris client secret to vendor or Zwapgrid support. Include the vendor error ID and client ID when required for troubleshooting.
Last updated
Was this helpful?
