RULE CHANGE
Affiliate API
Giveaway codes endpoint documentation updated to include revoked status and explain when codes become unredeemable.
What this means
The GET /v1/affiliate/giveaway-codes endpoint response now includes revoked as a possible status value alongside available and redeemed. The status field description changed from "available until someone redeems it, then redeemed. Each code can be redeemed once" to explain that codes can also be revoked by the team before redemption, at which point they can no longer be redeemed.
▸ View exact changes
The change in place, line by line
Before Nov 15, 2026
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 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
After Nov 18, 2026
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, redeemed, or revoked. |
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 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. A code the team cancelled before anyone redeemed it is
+ revoked and can no longer be redeemed;
- 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
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. |
+
| Endpoint | Returns |
|---|---|
| GET /v1/affiliate/giveaway-codes | Your giveaway codes, newest first, and whether each is available, redeemed, or revoked. |
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 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;
+ can be redeemed once. A code the team cancelled before anyone redeemed it is
+ revoked and can no longer be redeemed;
- 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