RULE CHANGE
Authentication
Article adds information about Affiliate API keys and their endpoint access restrictions.
What this means
New section explains that Affiliate API keys access only /v1/affiliate endpoints and return 403 insufficient_scope errors on other endpoints; conversely, standard Read Only and Read And Trade keys return 403 on /v1/affiliate endpoints. No changes to existing Read Only or Read And Trade key permissions.
▸ View exact changes
What the page said before and after
Before Oct 13, 2026
Authentication
Source: https://docs.myfundedperpetuals.com/authentication
Authenticate requests with a MyFundedPerps API key.
Send your API key in the HTTP Authorization header with the Bearer scheme:
http theme={null}
Authorization: Bearer fp_live_...
Each API key has an access level and account boundary:
| Access level | Allowed requests |
|---|
| Read Only | Accounts, markets, quotes, positions, orders, and fills |
| Read And Trade | Read requests plus order and position changes |
Account access can cover every account you own or one selected challenge
account. Requests for an account outside the key's boundary return 404, the
same response used for an account you do not own. Read-only keys receive 403
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
After Nov 11, 2026
Authentication
Source: https://docs.myfundedperpetuals.com/authentication
Authenticate requests with a MyFundedPerps API key.
Send your API key in the HTTP Authorization header with the Bearer scheme:
http theme={null}
Authorization: Bearer fp_live_...
Each API key has an access level and account boundary:
| Access level | Allowed requests |
|---|
| Read Only | Accounts, markets, quotes, positions, orders, and fills |
| Read And Trade | Read requests plus order and position changes |
+ Affiliate API keys, created on the API tab of the Affiliates page, are a
+ separate kind of live key that reads only the /v1/affiliate endpoints; see
+ Affiliate API. They receive 403 with the code
+ insufficient_scope on every other endpoint that needs a key, and the keys
+ above receive the same 403 on /v1/affiliate endpoints.
Account access can cover every account you own or one selected challenge
account. Requests for an account outside the key's boundary return 404, the
same response used for an account you do not own. Read-only keys receive 403
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
Authentication
Source: https://docs.myfundedperpetuals.com/authentication
Authenticate requests with a MyFundedPerps API key.
Send your API key in the HTTP Authorization header with the Bearer scheme:
http theme={null}
Authorization: Bearer fp_live_...
Each API key has an access level and account boundary:
| Access level | Allowed requests |
|---|
| Read Only | Accounts, markets, quotes, positions, orders, and fills |
| Read And Trade | Read requests plus order and position changes |
+ Affiliate API keys, created on the API tab of the Affiliates page, are a
+ separate kind of live key that reads only the /v1/affiliate endpoints; see
+ Affiliate API. They receive 403 with the code
+ insufficient_scope on every other endpoint that needs a key, and the keys
+ above receive the same 403 on /v1/affiliate endpoints.
Account access can cover every account you own or one selected challenge
account. Requests for an account outside the key's boundary return 404, the
same response used for an account you do not own. Read-only keys receive 403
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