RULE CHANGE
Affiliate API
Affiliate API documentation expanded to include giveaway code access and management via new endpoint.
What this means
The affiliate API key now grants access to giveaway codes in addition to existing data; a new GET /v1/affiliate/giveaway-codes endpoint was added to list codes with their status (available or redeemed), source, reward details, and redemption restrictions; the warning text was updated to note that holders of an affiliate key can copy unredeemed giveaway codes; cursor pagination now applies to giveaway codes alongside orders and payouts; the fperp CLI tool gained a new list-affiliate-giveaway-codes command.
▸ View exact changes
The change in place, line by line
Before Nov 12, 2026
Affiliate API
Source: https://docs.myfundedperpetuals.com/affiliate-api
− Read your affiliate summary, traffic and sales stats, orders, campaigns, and payouts with an affiliate API key.
Affiliate API keys let your own dashboards, spreadsheets, and bots read the
same figures as the Affiliates page.
They are read-only and separate from trading API keys: an affiliate key cannot
trade or see your trading accounts, and you do not need a trading account to
create one.
Create a key
Affiliate keys are available to active affiliates.
1. Open the Affiliates page and
select the API tab.
2. In the API Access card, select Create API Key.
3. Optionally name the key, then select Email Me a Code.
4. Enter the six-digit code from the email and select Create API Key.
5. Copy the key and store it somewhere safe. The full key is shown only once.
In the iOS app, open Affiliates, then API to create, copy, and revoke
the same affiliate keys. Email verification is still required. Save a newly
created key before closing its sheet: reopening the list does not reveal it.
You can hold up to five affiliate keys. The card lists each key's name, the
start of the key, and when it was created. Select Revoke to delete a key;
requests using it stop working right away. Affiliate keys do not appear in
API Key Settings, and trading keys do not appear in the
API Access card.
[!WARNING]
Treat an affiliate key like a password. Anyone holding it can read your
− affiliate earnings, orders, and payout history. Revoke a key you no longer use
− or that may have been exposed.
What an affiliate key can read
Send the key as a Bearer token to https://developers.myfundedperpetuals.com,
the same live host as the trading API. Affiliate keys are
live keys: they do not work on the sandbox host.
bash theme={null}
curl https://developers.myfundedperpetuals.com/v1/affiliate
-H "Authorization: Bearer $FP_AFFILIATE_KEY"
| Endpoint | Returns |
|---|---|
| GET /v1/affiliate | Your codes, tier, commission rate, referrals, revenue, earnings, payout balances. |
| GET /v1/affiliate/stats | Clicks, visitors, sign-ups, purchasers, orders, revenue, and commission by period. |
| GET /v1/affiliate/orders | Your commission history, newest first. |
| GET /v1/affiliate/campaigns | Every campaign link you created, including archived ones. |
| GET /v1/affiliate/payouts | Your payout requests, newest first. |
Every other endpoint that needs a key answers an affiliate key with 403 and
the code insufficient_scope. In the same way, trading keys, test keys, and
CLI or MCP sign-ins cannot read /v1/affiliate endpoints. The full request
and response schemas are in the REST Reference.
If your affiliate account is suspended, every /v1/affiliate request returns
404 with the code affiliate_not_found until the account is active again.
Your keys are kept and start working again when access returns.
Units and formats
- All amounts are US dollars as decimal numbers, such as 125.5.
- Times are Unix timestamps in milliseconds.
- Periods and dates use UTC days, like the Analytics tab.
- Response fields use snake_case, and errors use the API's standard
Orders
GET /v1/affiliate/orders lists the same orders as Commission History.
Each order has an id, the order_number printed on the customer's invoice,
the product, placed_at, the order amount, and its commission_amount,
commission_pct, and commission_status (pending, earned, refunded,
ineligible, no_code, or chargeback).
Orders never include who bought or which discount code they used.
Payouts
GET /v1/affiliate/payouts lists your payout requests with their id,
amount, status (pending, paid, or rejected), method (rise or
store_credit), requested_at, and paid_at. Payout destinations, such as
the email address a payout was sent to, are never returned.
Paging, limits, and errors
− Orders and payouts use the API's standard
cursor pagination: set limit from 1 to 100 (default 50) and
send next_cursor back as cursor while has_more is true.
Affiliate requests share the same request limits as every other API request;
see Errors and rate limits. A 503 with the code
affiliate_data_preparing means figures are briefly being rebuilt; retry
after the Retry-After delay.
Command line
The fperp CLI includes get-affiliate-summary,
get-affiliate-stats, list-affiliate-orders, list-affiliate-campaigns,
− and list-affiliate-payouts. Pass your affiliate key in the
FPERP_API_KEY environment variable:
bash theme={null}
FPERP_API_KEY="$FP_AFFILIATE_KEY" fperp get-affiliate-summary
fperp login checks a key by reading your trading accounts, which an
affiliate key cannot do, so it does not save an affiliate key unless you add
--no-verify. The MCP server does not offer affiliate tools.
After Nov 15, 2026
Affiliate API
Source: https://docs.myfundedperpetuals.com/affiliate-api
+ Read your affiliate summary, traffic and sales stats, orders, campaigns, payouts, and giveaway codes with an affiliate API key.
Affiliate API keys let your own dashboards, spreadsheets, and bots read the
same figures as the Affiliates page.
They are read-only and separate from trading API keys: an affiliate key cannot
trade or see your trading accounts, and you do not need a trading account to
create one.
Create a key
Affiliate keys are available to active affiliates.
1. Open the Affiliates page and
select the API tab.
2. In the API Access card, select Create API Key.
3. Optionally name the key, then select Email Me a Code.
4. Enter the six-digit code from the email and select Create API Key.
5. Copy the key and store it somewhere safe. The full key is shown only once.
In the iOS app, open Affiliates, then API to create, copy, and revoke
the same affiliate keys. Email verification is still required. Save a newly
created key before closing its sheet: reopening the list does not reveal it.
You can hold up to five affiliate keys. The card lists each key's name, the
start of the key, and when it was created. Select Revoke to delete a key;
requests using it stop working right away. Affiliate keys do not appear in
API Key Settings, and trading keys do not appear in the
API Access card.
[!WARNING]
Treat an affiliate key like a password. Anyone holding it can read your
+ affiliate earnings, orders, and payout history, and copy your unredeemed
+ giveaway codes. Revoke a key you no longer use or that may have been exposed.
What an affiliate key can read
Send the key as a Bearer token to https://developers.myfundedperpetuals.com,
the same live host as the trading API. Affiliate keys are
live keys: they do not work on the sandbox host.
bash theme={null}
curl https://developers.myfundedperpetuals.com/v1/affiliate
-H "Authorization: Bearer $FP_AFFILIATE_KEY"
| Endpoint | Returns |
|---|---|
| GET /v1/affiliate | Your codes, tier, commission rate, referrals, revenue, earnings, payout balances. |
| GET /v1/affiliate/stats | Clicks, visitors, sign-ups, purchasers, orders, revenue, and commission by period. |
| GET /v1/affiliate/orders | Your commission history, newest first. |
| GET /v1/affiliate/campaigns | Every campaign link you created, including archived ones. |
| GET /v1/affiliate/payouts | Your payout requests, newest first. |
+ GET /v1/affiliate/giveaway-codes | Your giveaway codes, newest first, and whether each is available or redeemed.
Every other endpoint that needs a key answers an affiliate key with 403 and
the code insufficient_scope. In the same way, trading keys, test keys, and
CLI or MCP sign-ins cannot read /v1/affiliate endpoints. The full request
and response schemas are in the REST Reference.
If your affiliate account is suspended, every /v1/affiliate request returns
404 with the code affiliate_not_found until the account is active again.
Your keys are kept and start working again when access returns.
Units and formats
- All amounts are US dollars as decimal numbers, such as 125.5.
- Times are Unix timestamps in milliseconds.
- Periods and dates use UTC days, like the Analytics tab.
- Response fields use snake_case, and errors use the API's standard
Orders
GET /v1/affiliate/orders lists the same orders as Commission History.
Each order has an id, the order_number printed on the customer's invoice,
the product, placed_at, the order amount, and its commission_amount,
commission_pct, and commission_status (pending, earned, refunded,
ineligible, no_code, or chargeback).
Orders never include who bought or which discount code they used.
Payouts
GET /v1/affiliate/payouts lists your payout requests with their id,
amount, status (pending, paid, or rejected), method (rise or
store_credit), requested_at, and paid_at. Payout destinations, such as
the email address a payout was sent to, are never returned.
+ Giveaway codes
+ GET /v1/affiliate/giveaway-codes lists the same codes as the Giveaways
+ tab: codes from your reward tiers, codes the team issued you, and codes you
+ bought. Each code has:
+ - id and code, the text to share;
+ - status: available until someone redeems it, then redeemed. Each code
+ can be redeemed once;
+ - source: tier_reward, team, or purchased;
+ - reward: either { "kind": "account", ... } with the account's
+ challenge_tier_key, model, plan, size, starting_balance, and
+ profit_split_pct, or { "kind": "case", "case_type": ... } for a reward
+ case;
+ - first_time_redeemers_only and account_requirement (without_account,
+ with_account, or null for anyone), which limit who can redeem it;
+ - issued_at, redeemed_at, and redeemed_by_email, a partly hidden email
+ such as fo•••@e•••.com, the same as on the Giveaways tab.
+ The list cannot be filtered by status. To find the codes still available,
+ read every page and keep the ones whose status is available. The API does
+ not know which codes you have already sent to someone, so a bot that gives
+ codes away should record each code it sends and skip those codes next time.
+ A code you sent stays available until its recipient redeems it.
+ bash theme={null}
+ curl "https://developers.myfundedperpetuals.com/v1/affiliate/giveaway-codes?limit=100"
+ -H "Authorization: Bearer $FP_AFFILIATE_KEY"
+ [!WARNING]
+ Anyone holding your affiliate key can read and redeem your available giveaway
+ codes. Keep the key on the server your bot runs on, never in a public channel
+ or client-side code.
Paging, limits, and errors
+ Orders, payouts, and giveaway codes use the API's standard
cursor pagination: set limit from 1 to 100 (default 50) and
send next_cursor back as cursor while has_more is true.
Affiliate requests share the same request limits as every other API request;
see Errors and rate limits. A 503 with the code
affiliate_data_preparing means figures are briefly being rebuilt; retry
after the Retry-After delay.
Command line
The fperp CLI includes get-affiliate-summary,
get-affiliate-stats, list-affiliate-orders, list-affiliate-campaigns,
+ list-affiliate-payouts, and list-affiliate-giveaway-codes. Pass your affiliate key in the
FPERP_API_KEY environment variable:
bash theme={null}
FPERP_API_KEY="$FP_AFFILIATE_KEY" fperp get-affiliate-summary
fperp login checks a key by reading your trading accounts, which an
affiliate key cannot do, so it does not save an affiliate key unless you add
--no-verify. The MCP server does not offer affiliate tools.
Affiliate API
Source: https://docs.myfundedperpetuals.com/affiliate-api
− Read your affiliate summary, traffic and sales stats, orders, campaigns, and payouts with an affiliate API key.
+ Read your affiliate summary, traffic and sales stats, orders, campaigns, payouts, and giveaway codes with an affiliate API key.
Affiliate API keys let your own dashboards, spreadsheets, and bots read the
same figures as the Affiliates page.
They are read-only and separate from trading API keys: an affiliate key cannot
trade or see your trading accounts, and you do not need a trading account to
create one.
Create a key
Affiliate keys are available to active affiliates.
1. Open the Affiliates page and
select the API tab.
2. In the API Access card, select Create API Key.
3. Optionally name the key, then select Email Me a Code.
4. Enter the six-digit code from the email and select Create API Key.
5. Copy the key and store it somewhere safe. The full key is shown only once.
In the iOS app, open Affiliates, then API to create, copy, and revoke
the same affiliate keys. Email verification is still required. Save a newly
created key before closing its sheet: reopening the list does not reveal it.
You can hold up to five affiliate keys. The card lists each key's name, the
start of the key, and when it was created. Select Revoke to delete a key;
requests using it stop working right away. Affiliate keys do not appear in
API Key Settings, and trading keys do not appear in the
API Access card.
[!WARNING]
Treat an affiliate key like a password. Anyone holding it can read your
− affiliate earnings, orders, and payout history. Revoke a key you no longer use
− or that may have been exposed.
+ affiliate earnings, orders, and payout history, and copy your unredeemed
+ giveaway codes. Revoke a key you no longer use or that may have been exposed.
What an affiliate key can read
Send the key as a Bearer token to https://developers.myfundedperpetuals.com,
the same live host as the trading API. Affiliate keys are
live keys: they do not work on the sandbox host.
bash theme={null}
curl https://developers.myfundedperpetuals.com/v1/affiliate
-H "Authorization: Bearer $FP_AFFILIATE_KEY"
| Endpoint | Returns |
|---|---|
| GET /v1/affiliate | Your codes, tier, commission rate, referrals, revenue, earnings, payout balances. |
| GET /v1/affiliate/stats | Clicks, visitors, sign-ups, purchasers, orders, revenue, and commission by period. |
| GET /v1/affiliate/orders | Your commission history, newest first. |
| GET /v1/affiliate/campaigns | Every campaign link you created, including archived ones. |
| GET /v1/affiliate/payouts | Your payout requests, newest first. |
+
| Endpoint | Returns |
|---|---|
| GET /v1/affiliate/giveaway-codes | Your giveaway codes, newest first, and whether each is available or redeemed. |
Every other endpoint that needs a key answers an affiliate key with 403 and
the code insufficient_scope. In the same way, trading keys, test keys, and
CLI or MCP sign-ins cannot read /v1/affiliate endpoints. The full request
and response schemas are in the REST Reference.
If your affiliate account is suspended, every /v1/affiliate request returns
404 with the code affiliate_not_found until the account is active again.
Your keys are kept and start working again when access returns.
Units and formats
- All amounts are US dollars as decimal numbers, such as 125.5.
- Times are Unix timestamps in milliseconds.
- Periods and dates use UTC days, like the Analytics tab.
- Response fields use snake_case, and errors use the API's standard
Orders
GET /v1/affiliate/orders lists the same orders as Commission History.
Each order has an id, the order_number printed on the customer's invoice,
the product, placed_at, the order amount, and its commission_amount,
commission_pct, and commission_status (pending, earned, refunded,
ineligible, no_code, or chargeback).
Orders never include who bought or which discount code they used.
Payouts
GET /v1/affiliate/payouts lists your payout requests with their id,
amount, status (pending, paid, or rejected), method (rise or
store_credit), requested_at, and paid_at. Payout destinations, such as
the email address a payout was sent to, are never returned.
+ Giveaway codes
+ GET /v1/affiliate/giveaway-codes lists the same codes as the Giveaways
+ tab: codes from your reward tiers, codes the team issued you, and codes you
+ bought. Each code has:
+ - id and code, the text to share;
+ - status: available until someone redeems it, then redeemed. Each code
+ can be redeemed once;
+ - source: tier_reward, team, or purchased;
+ - reward: either { "kind": "account", ... } with the account's
+ challenge_tier_key, model, plan, size, starting_balance, and
+ profit_split_pct, or { "kind": "case", "case_type": ... } for a reward
+ case;
+ - first_time_redeemers_only and account_requirement (without_account,
+ with_account, or null for anyone), which limit who can redeem it;
+ - issued_at, redeemed_at, and redeemed_by_email, a partly hidden email
+ such as fo•••@e•••.com, the same as on the Giveaways tab.
+ The list cannot be filtered by status. To find the codes still available,
+ read every page and keep the ones whose status is available. The API does
+ not know which codes you have already sent to someone, so a bot that gives
+ codes away should record each code it sends and skip those codes next time.
+ A code you sent stays available until its recipient redeems it.
+ bash theme={null}
+ curl "https://developers.myfundedperpetuals.com/v1/affiliate/giveaway-codes?limit=100"
+ -H "Authorization: Bearer $FP_AFFILIATE_KEY"
+ [!WARNING]
+ Anyone holding your affiliate key can read and redeem your available giveaway
+ codes. Keep the key on the server your bot runs on, never in a public channel
+ or client-side code.
Paging, limits, and errors
− Orders and payouts use the API's standard
+ Orders, payouts, and giveaway codes use the API's standard
cursor pagination: set limit from 1 to 100 (default 50) and
send next_cursor back as cursor while has_more is true.
Affiliate requests share the same request limits as every other API request;
see Errors and rate limits. A 503 with the code
affiliate_data_preparing means figures are briefly being rebuilt; retry
after the Retry-After delay.
Command line
The fperp CLI includes get-affiliate-summary,
get-affiliate-stats, list-affiliate-orders, list-affiliate-campaigns,
− and list-affiliate-payouts. Pass your affiliate key in the
+ list-affiliate-payouts, and list-affiliate-giveaway-codes. Pass your affiliate key in the
FPERP_API_KEY environment variable:
bash theme={null}
FPERP_API_KEY="$FP_AFFILIATE_KEY" fperp get-affiliate-summary
fperp login checks a key by reading your trading accounts, which an
affiliate key cannot do, so it does not save an affiliate key unless you add
--no-verify. The MCP server does not offer affiliate tools.