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

​
Testing levels

​
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

​
Test user credentials

Use these credentials to log in to Flinks Capital in the Toolbox: 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. 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.