RULE CHANGE
Sandbox and test keys
Added instructions for hiding sandbox accounts in the account switcher using a Filter option.
What this means
A new Hide Sandbox Accounts filter option was added to the account switcher, allowing users to hide or show sandbox accounts as needed. Sandbox accounts still enforce evaluation rules and can breach, and still carry a Sandbox badge and never show funded-stage progression, as before.
▸ View exact changes
What the page said before and after
Before Oct 11, 2026
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
resources return 404; a client order ID lookup returns an empty list.
- Archived accounts and their orders, positions, and strategy history are
unavailable through trading endpoints in either API environment, including
previously successful trading-request replays.
- Sandbox accounts are excluded from analytics, leaderboards, certificates,
and payouts. They exist only for integration testing. In the web app they
carry a Sandbox badge in the account switcher, and their dashboard
never shows funded-stage progression because a sandbox account cannot
− become funded.
- Sandbox trading still enforces evaluation rules, so a sandbox account can
breach. That is useful for testing how your integration handles rejections
and account failure.
- Reaching the profit target ends a sandbox account as passed. A sandbox pass
does not lead to identity verification, an agreement, or a funded account.
Go live
When your integration works in the sandbox, create a live key with the same
access level, point your client at
https://developers.myfundedperpetuals.com, and select the challenge accounts
it should reach. No other code changes are needed.
After Oct 15, 2026
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
resources return 404; a client order ID lookup returns an empty list.
- Archived accounts and their orders, positions, and strategy history are
unavailable through trading endpoints in either API environment, including
previously successful trading-request replays.
- Sandbox accounts are excluded from analytics, leaderboards, certificates,
and payouts. They exist only for integration testing. In the web app they
carry a Sandbox badge in the account switcher, and their dashboard
never shows funded-stage progression because a sandbox account cannot
+ become funded. To keep them out of the account switcher, open Filter
+ and check Hide Sandbox Accounts; uncheck it to show them again.
- Sandbox trading still enforces evaluation rules, so a sandbox account can
breach. That is useful for testing how your integration handles rejections
and account failure.
- Reaching the profit target ends a sandbox account as passed. A sandbox pass
does not lead to identity verification, an agreement, or a funded account.
Go live
When your integration works in the sandbox, create a live key with the same
access level, point your client at
https://developers.myfundedperpetuals.com, and select the challenge accounts
it should reach. No other code changes are needed.
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
resources return 404; a client order ID lookup returns an empty list.
- Archived accounts and their orders, positions, and strategy history are
unavailable through trading endpoints in either API environment, including
previously successful trading-request replays.
- Sandbox accounts are excluded from analytics, leaderboards, certificates,
and payouts. They exist only for integration testing. In the web app they
carry a Sandbox badge in the account switcher, and their dashboard
never shows funded-stage progression because a sandbox account cannot
− become funded.
+ become funded. To keep them out of the account switcher, open Filter
+ and check Hide Sandbox Accounts; uncheck it to show them again.
- Sandbox trading still enforces evaluation rules, so a sandbox account can
breach. That is useful for testing how your integration handles rejections
and account failure.
- Reaching the profit target ends a sandbox account as passed. A sandbox pass
does not lead to identity verification, an agreement, or a funded account.
Go live
When your integration works in the sandbox, create a live key with the same
access level, point your client at
https://developers.myfundedperpetuals.com, and select the challenge accounts
it should reach. No other code changes are needed.