RULE CHANGE
Sandbox and test keys
Added section explaining that sandbox accounts don't send breach or status emails by default, requiring manual enablement in settings.
What this means
New content describes that sandbox accounts do not send breach or status emails by default, but traders can enable Sandbox Account Emails in the Sandbox Accounts panel to receive them; in-app notifications remain unaffected regardless of this setting.
▸ View exact changes
What the page said before and after
Before Oct 15, 2026
Create more sandbox accounts
In API Key settings,
find Sandbox Accounts and select Create Sandbox Account. You can create
another account while your other sandbox accounts are still active, without
creating another API key. Each starts with a \$100,000 simulated balance.
The panel lists each account's name, account number, and status.
Every existing test key automatically gains access to the new account. Use the
account ID returned by GET /v1/accounts to select it in API requests.
The ten-account lifetime limit includes active, passed, failed, and closed
sandbox accounts. Creating more accounts requires the same active sandbox
access as creating test keys. When access lapses or the limit is reached,
Create Sandbox Account is unavailable and the panel explains why.
Differences from live
- Test keys authenticate only on sandbox.myfundedperpetuals.com; live keys
authenticate only on developers.myfundedperpetuals.com. Using a key on the
wrong host returns 401 with a message naming the correct host.
- The account stream works the same way: test keys
connect to wss://account-stream.myfundedperpetuals.com/v1/sandbox/stream
and receive only sandbox accounts.
- Sandbox accounts never appear in live API responses, and challenge accounts
never appear in sandbox responses. This applies to direct position, order,
TWAP/VWAP, and scaled-order IDs, client order IDs, modifications, cancellations,
and idempotent retries. A known ID does not grant access across environments
or outside the accounts selected for the credential. Inaccessible individual
After Oct 22, 2026
Create more sandbox accounts
In API Key settings,
find Sandbox Accounts and select Create Sandbox Account. You can create
another account while your other sandbox accounts are still active, without
creating another API key. Each starts with a \$100,000 simulated balance.
The panel lists each account's name, account number, and status.
Every existing test key automatically gains access to the new account. Use the
account ID returned by GET /v1/accounts to select it in API requests.
The ten-account lifetime limit includes active, passed, failed, and closed
sandbox accounts. Creating more accounts requires the same active sandbox
access as creating test keys. When access lapses or the limit is reached,
Create Sandbox Account is unavailable and the panel explains why.
+ Sandbox account emails
+ Sandbox accounts do not send breach or status emails by default, so a test
+ breach never looks like a problem with a real challenge account. To receive
+ them, turn on Sandbox Account Emails in the Sandbox Accounts panel.
+ In-app notifications for sandbox accounts are unaffected.
Differences from live
- Test keys authenticate only on sandbox.myfundedperpetuals.com; live keys
authenticate only on developers.myfundedperpetuals.com. Using a key on the
wrong host returns 401 with a message naming the correct host.
- The account stream works the same way: test keys
connect to wss://account-stream.myfundedperpetuals.com/v1/sandbox/stream
and receive only sandbox accounts.
- Sandbox accounts never appear in live API responses, and challenge accounts
never appear in sandbox responses. This applies to direct position, order,
TWAP/VWAP, and scaled-order IDs, client order IDs, modifications, cancellations,
and idempotent retries. A known ID does not grant access across environments
or outside the accounts selected for the credential. Inaccessible individual
Create more sandbox accounts
In API Key settings,
find Sandbox Accounts and select Create Sandbox Account. You can create
another account while your other sandbox accounts are still active, without
creating another API key. Each starts with a \$100,000 simulated balance.
The panel lists each account's name, account number, and status.
Every existing test key automatically gains access to the new account. Use the
account ID returned by GET /v1/accounts to select it in API requests.
The ten-account lifetime limit includes active, passed, failed, and closed
sandbox accounts. Creating more accounts requires the same active sandbox
access as creating test keys. When access lapses or the limit is reached,
Create Sandbox Account is unavailable and the panel explains why.
+ Sandbox account emails
+ Sandbox accounts do not send breach or status emails by default, so a test
+ breach never looks like a problem with a real challenge account. To receive
+ them, turn on Sandbox Account Emails in the Sandbox Accounts panel.
+ In-app notifications for sandbox accounts are unaffected.
Differences from live
- Test keys authenticate only on sandbox.myfundedperpetuals.com; live keys
authenticate only on developers.myfundedperpetuals.com. Using a key on the
wrong host returns 401 with a message naming the correct host.
- The account stream works the same way: test keys
connect to wss://account-stream.myfundedperpetuals.com/v1/sandbox/stream
and receive only sandbox accounts.
- Sandbox accounts never appear in live API responses, and challenge accounts
never appear in sandbox responses. This applies to direct position, order,
TWAP/VWAP, and scaled-order IDs, client order IDs, modifications, cancellations,
and idempotent retries. A known ID does not grant access across environments
or outside the accounts selected for the credential. Inaccessible individual