Step 1: Generate a Sandbox Key
Note that only dashboard admins have access to both sandbox and prod API keys.
Please ask your dashboard admin for access if you don’t have it
Please ask your dashboard admin for access if you don’t have it
- Go to https://dashboard.bridge.xyz/ and log in with your email.
- Then, ensure the “Sandbox” toggle is turned on (blue).
- Then, hit the button to generate a sandbox key.
- Sandbox keys should be prefixed with
sk-test
.
Step 2: Hit an API
Bridge’s sandbox is currently functional with the customer creation and KYC process. For example, here is how you can create a Bridge customer.Note that the sandbox base url is https://api.sandbox.bridge.xyz
- Create a customer
- Fetch that customer
- Examine simulated KYC
- Creating fake liquidation addresses, transfers and fiat deposit instructions (Note: there is no real money movement in Sandbox)
Differences with Production
Sandbox differs from production in a few key areas. We highly recommend using the Sandbox only to test API request/response schemas and Production itself for any other kind of testing. Onboarding/KYC- Customers must be created via the API; they cannot be created using kyc links.
- Customers are automatically approved (no KYC/KYB flow)
- Sandbox is subject to arbitrary rate limits; we may drop your requests anytime.
- The signed agreement ID in production cannot be arbitrary
- While in production you can have multiple users under the same Developer Account, in Sandbox each of those users will be scoped under their own unique Developer Account. In particular, changes made by one user in the sandbox won’t be visible to other users even if those users share a developer account in production.
- There is no real money movement in Sandbox.
- Plaid does not work in Sandbox.
- There is no testnet support in Sandbox.
- Virtual Accounts, Static Memos, Liquidation Addresses, and Transfers are created with dummy data.
- There are no webhooks fired in sandbox.