Skip to main content

​
Quick Start

Sandbox accounts use a special email format and a shared password. Pick a scenario, choose any identifier, and log in.
ScenarioEmail formatPasswordOTP
Creator (no 2FA){identifier}@creator.sandbox.comgood-password—
Creator (app OTP){identifier}@creator-otp.sandbox.comgood-password123456
Fan (no 2FA){identifier}@fan.sandbox.comgood-password—
Fan (app OTP){identifier}@fan-otp.sandbox.comgood-password123456
Examples: 
[email protected]          // Creator without 2FA
[email protected]      // Creator with app OTP 123456
[email protected]             // Fan without 2FA
[email protected]         // Fan with app OTP 123456
Any identifier works (e.g., demo, user123, etc.). The domain and scenario control the behavior.

​
What You Can Test

  • Link (Hosted or Embed): Complete full authentication flows, including OTP when using *-otp scenarios
  • Access (Managed and Proxy): Call endpoints using the resulting connectionId and receive realistic fixture payloads
  • Webhooks: Receive simulated events (e.g., connection.created, connection.updated, connection.expired)

​
Notes & Limitations

  • Data is deterministic and may reset; treat responses as fixtures, not persistent storage
  • Behavior and APIs are identical to Live; the only change is the data source

​
Environment Selection

  • Use a Sandbox API key (sk_sandbox_...) to enable Sandbox behavior across Link and Access
  • No additional headers are required; the environment is inferred from the key
  • You can set everything up with Sandbox first, then switch to a Live key without changing code

​
Troubleshooting

  • Wrong password: Ensure you use good-password
  • OTP required: Only for creator-otp and fan-otp; the OTP is 123456
  • Invalid email: Verify the scenario domain (e.g., creator.sandbox.com, fan-otp.sandbox.com)

​
Next Steps

Environments Overview

Learn how environments are selected and differ

Link API

Create sessions and get connection IDs

Access API

Query data using your connection ID