RULE CHANGE
Authentication
Restricted-countries endpoint changed from requiring a key to being public.
What this means
The restricted-countries endpoint is now listed as public and does not require an API key, whereas previously only the API information and tradable-market catalog endpoints were public. Account state, quotes, positions, and orders still require a key.
▸ View exact changes
What the page said before and after
Before Oct 11, 2026
when they attempt a trading request.
Copy trading follows the same account boundary. A lead order requires access to
its lead and every configured follower in the same environment. A key limited
to the lead account cannot place the lead trade while that copy group is
enabled. The request returns 404 with account_not_found before any order is
created; followers are never silently omitted. Use a key covering the complete
group or manage the trade on the website.
Modifications, cancellations, and protective-exit changes also require access
to every copied account they would affect. This includes outstanding copied
orders from a group that has since been disabled. A live key never grants
access to a sandbox follower, even when the website configuration includes it.
Keys created before scoped access was introduced retain read and trading access
− to every owned account until they are revoked. The API information and
− tradable-market catalog endpoints are public; account state, quotes, positions,
− and orders require a key.
Environments
Every key belongs to one environment, named by its prefix and served on its
own hostname:
| Environment | Key prefix | Base URL | Reaches |
|---|---|---|---|
| Live | fp_live_ | https://developers.myfundedperpetuals.com | Your challenge accounts |
| Test | fp_test_ | https://sandbox.myfundedperpetuals.com | Your sandbox accounts only |
A key presented on the other environment's host returns 401 with a message
naming the correct host. Test keys and sandbox accounts are covered in
Sandbox and test keys.
CLI sessions
The fperp command-line tool can sign in without a manually created API key.
Running fperp login opens your browser to an approval page; approving mints
After Oct 13, 2026
when they attempt a trading request.
Copy trading follows the same account boundary. A lead order requires access to
its lead and every configured follower in the same environment. A key limited
to the lead account cannot place the lead trade while that copy group is
enabled. The request returns 404 with account_not_found before any order is
created; followers are never silently omitted. Use a key covering the complete
group or manage the trade on the website.
Modifications, cancellations, and protective-exit changes also require access
to every copied account they would affect. This includes outstanding copied
orders from a group that has since been disabled. A live key never grants
access to a sandbox follower, even when the website configuration includes it.
Keys created before scoped access was introduced retain read and trading access
+ to every owned account until they are revoked. The API information,
+ tradable-market catalog, and restricted-countries endpoints are public; account
+ state, quotes, positions, and orders require a key.
Environments
Every key belongs to one environment, named by its prefix and served on its
own hostname:
| Environment | Key prefix | Base URL | Reaches |
|---|---|---|---|
| Live | fp_live_ | https://developers.myfundedperpetuals.com | Your challenge accounts |
| Test | fp_test_ | https://sandbox.myfundedperpetuals.com | Your sandbox accounts only |
A key presented on the other environment's host returns 401 with a message
naming the correct host. Test keys and sandbox accounts are covered in
Sandbox and test keys.
CLI sessions
The fperp command-line tool can sign in without a manually created API key.
Running fperp login opens your browser to an approval page; approving mints
when they attempt a trading request.
Copy trading follows the same account boundary. A lead order requires access to
its lead and every configured follower in the same environment. A key limited
to the lead account cannot place the lead trade while that copy group is
enabled. The request returns 404 with account_not_found before any order is
created; followers are never silently omitted. Use a key covering the complete
group or manage the trade on the website.
Modifications, cancellations, and protective-exit changes also require access
to every copied account they would affect. This includes outstanding copied
orders from a group that has since been disabled. A live key never grants
access to a sandbox follower, even when the website configuration includes it.
Keys created before scoped access was introduced retain read and trading access
− to every owned account until they are revoked. The API information and
− tradable-market catalog endpoints are public; account state, quotes, positions,
− and orders require a key.
+ to every owned account until they are revoked. The API information,
+ tradable-market catalog, and restricted-countries endpoints are public; account
+ state, quotes, positions, and orders require a key.
Environments
Every key belongs to one environment, named by its prefix and served on its
own hostname:
| Environment | Key prefix | Base URL | Reaches |
|---|---|---|---|
| Live | fp_live_ | https://developers.myfundedperpetuals.com | Your challenge accounts |
| Test | fp_test_ | https://sandbox.myfundedperpetuals.com | Your sandbox accounts only |
A key presented on the other environment's host returns 401 with a message
naming the correct host. Test keys and sandbox accounts are covered in
Sandbox and test keys.
CLI sessions
The fperp command-line tool can sign in without a manually created API key.
Running fperp login opens your browser to an approval page; approving mints