The SPAR sandbox environment is available for testing during development. The sandbox feature allows you to build integrations without fetching live SPAR data and incurring production charges.
To use the sandbox environment, a dedicated Sandbox API service must be configured in Creditsafe's backend. Request and response structures mirror production behaviour.
Authorization works the same way as in live environments using CONNECT Authenticate, but credentials and tokens are environment-specific and not interchangeable.
In addition to CONNECT authentication, SPAR production usage requires valid SPAR authorization from the Swedish Tax Agency (Skatteverket). See SPAR Access Authorization for details.
SPAR Endpoint:
https://se-webservice-sandbox.apps.creditsafe.com/sparHealth Check:
https://se-webservice-sandbox.apps.creditsafe.com/spar/healthWhen testing in sandbox:
- Use test personal identity numbers provided by Creditsafe
- Test both successful and error scenarios
- Verify handling of all response fields
- Test optional parameters such as
relation,transactionid, andlanguage
Developers are encouraged to structure sandbox requests exactly as they will be sent in production. This simplifies deployment and reduces integration risk.
To access the sandbox environment:
- You will need a signed agreement with Creditsafe
- Our sales team will facilitate this agreement
- The integration team will provide sandbox credentials and test guidance
The Creditsafe integration team (integration@creditsafe.se) can provide test data support and onboarding assistance.
At some point, you will need to transition the development environment to use the live services and verify that everything works as expected.
When making this switch, be cautious to avoid unintentionally generating credit reports through services like GetData or CAS, as this could trigger the sending of letters of disclosure.
Important: Using the SPAR API itself never results in letters of disclosure being sent.
When transitioning to production:
- Update your base URL from sandbox to production endpoints
- Use production credentials and production CONNECT Authenticate tokens
- Confirm SPAR authorization prerequisites are complete
- Validate request and response handling in a controlled rollout
While the sandbox environment mirrors the structure and format of responses from the live API, the data itself is synthetic and may not be logically consistent or realistic. This environment is intended solely for integration testing and development purposes.