Testing Environments

Understand the three levels of testing available at Flinks: Sandbox, Toolbox, and Production.

Flinks provides multiple testing environments so you can develop, test, and validate your integration before going live.

Testing levels

Environment	Purpose	Real FI connections	Credentials
Sandbox (Dashboard)	Explore the Dashboard with sample data	No	Found in Dashboard Settings > Environments
Toolbox	Full API sandbox with dummy data from Flinks Capital	No	Shared public credentials (below)
Production	Live environment with real financial institutions	Yes	Unique credentials from Flinks

Toolbox (API sandbox)

The Toolbox is your primary development environment for testing API calls. It uses a shared sandbox instance with a dummy financial institution called Flinks Capital.

Toolbox credentials

Credential	Value
Instance	toolbox
API Base URL	https://toolbox-api.private.fin.ag
Iframe Base URL	https://toolbox-iframe.private.fin.ag
customerId	43387ca6-0391-4c82-857d-70d95f087ecb
Secret key (flinks-auth-key)	c4569c54-e167-4d34-8de6-f4113bc82414
x-api-key	3d5266a8-b697-48d4-8de6-52e2e2662acc

Test user credentials

Use these credentials to log in to Flinks Capital in the Toolbox:

Username	Password	Description
Greatday	Everyday	Standard test account with MFA
greatday_nomfa	Everyday	Test account without MFA

For a full list of test scenarios (error testing, edge cases), see Test Users.

These are shared public sandbox credentials for testing only. Never use production credentials in the Toolbox or vice versa.

Dashboard sandbox

The Flinks Dashboard includes its own sandbox environment with pre-populated sample data. This is useful for exploring the Dashboard interface without needing to make API calls.

To access sandbox credentials in the Dashboard:

1. Navigate to Settings.
2. Go to the Environments tab.
3. Expand the Sandbox row to view your credentials.

Dashboard sandbox credentials are for exploring the Dashboard only. They will not work in API calls. Use the Toolbox credentials above for API testing.

Production environment

Your production environment uses a private instance with unique credentials provided by Flinks during onboarding.

Component	Format
API Base URL	https://{yourcompany}-api.private.fin.ag
Iframe Base URL	https://{yourcompany}-iframe.private.fin.ag
customerId	Unique GUID provided by Flinks

Before going live:

• Ensure all API calls and iframe URLs point to your production instance
• Verify your redirectUrl domains are whitelisted
• Test with Flinks Capital in production at no cost before connecting real accounts

Flinks instances are scoped by country — a single instance serves either Canadian or U.S. end-users, not both. If you onboard customers in both countries, you’ll be provisioned with two separate instances. See Instances and Data Residency for details.

FDX end-to-end testing

If you are using the Flinks Outbound (Open Banking) product with FDX endpoints, follow this procedure to test the full flow:

1. Prerequisites: Ensure you have your client_id and client_secret from Flinks onboarding.
2. Authorize: Call the /api/v1/authorize endpoint to initiate an OAuth connection with a test Data Provider.
3. Token exchange: Use the authorization code to obtain an access_token via the /Token endpoint.
4. Retrieve data: Call FDX endpoints (/accounts, /transactions) with the access_token.

For details on each endpoint, see the Outbound API Reference.