Testing in sandbox before you go live
What the Fiskil sandbox simulates, what it doesn't, and how to move from test consents to production.
The Fiskil sandbox lets you build and test your integration end to end before any real consumer data is involved. It mirrors production, so the integration you test is the integration you ship.
What the sandbox is for
Use the sandbox to exercise the full lifecycle of your integration:
- Authenticating with your API keys and creating end users.
- Running the consent flow against a sandbox institution.
- Fetching data across the Banking and Energy domains.
- Verifying how your application handles the responses.
The sandbox supports unlimited end users and consents, with realistic sample data across both banking and energy, so you can test at whatever volume you need.
What's simulated vs. real
- Simulated: the institution. Instead of a real bank or energy retailer, you connect to a sandbox provider with pre-built sample accounts. Authentication uses a one-time code sent to any email address you can access — no real bank credentials are involved.
- Real: everything else. You use the same console, the same API endpoints, and the same request and response shapes as production. See the Testing guide for the step-by-step walkthrough and sample account details.
Creating your first sandbox consent
- Create an API key pair under API Keys in the Fiskil Console, and exchange the credentials for an access token.
- Create an end user via the API.
- From the End-Users page in the console, select your user and click Create Auth Session, then open the link in a browser.
- Choose the sandbox provider (bank or energy retailer), complete the one-time code step with an email you can access, select an account, and confirm.
You now have a live sandbox consent and can start calling the data endpoints.
Sandbox access is set up per team
If you don't see the sandbox available for your team, contact Fiskil support and we'll enable it and sort out permissions.
Limits to keep in mind
Sandbox data is sample data — it's realistic in shape, but it won't reproduce every quirk of a specific real institution, such as institution-side outages, eligibility rules, or data-quality differences between data holders. Treat the sandbox as proof that your integration logic works, and plan a careful rollout for institution-specific behaviour.
The path to production
When your integration works end to end in the sandbox, the next step is production access and the go-live checks — see Moving to production and the Go Live Checklist.