RULE CHANGE
Trading with the API
Article expanded to clarify stop-market/take-profit fill mechanics and adds new price alerts API section with four endpoints.
What this means
Stop-market and take-profit order fill behavior clarified: orders can now fill at touch bid/ask when spread exceeds slippage cap (previously described as retaining ordinary current-quote execution), and slippage tolerance replaced the term slippage cap in one context. New price alerts feature added with POST /v1/price-alerts, PATCH /v1/price-alerts/{id}, POST /v1/price-alerts/{id}/rearm, and DELETE endpoints; alerts limit is 25 armed alerts; triggered alerts remain listed 90 days.
▸ View exact changes
What the page said before and after
Before Oct 31, 2026
cap. The quote's reference_price, reference_kind, and reference_time
identify its execution reference. An estimate does not reserve a price.
Conditional trigger policy
New TP/SL and other conditional orders use Last Price on Binance, Bybit and
Hyperliquid. This is selected by the server; no new request parameter is
required. An external condition follows its trigger
market's source, while execution uses its order market's book.
Existing orders keep their original trigger policy when their price or size is
modified. Canceling and replacing an order adopts the current policy. Copied
orders, partial fills and attached TP/SL inherit the originating order's policy,
including when they are created after this update. A trigger does not guarantee
its fill price. See TP/SL behavior.
− Eligible protective stop-market and take-profit market orders can use the first
− recorded bid or ask at or after their touch. The accepted price stays fixed during
− processing. Recent order or position changes, unavailable quote history, or a
− spread outside the slippage cap retain ordinary current-quote execution. Fees,
funding charges, loss limits, and liquidation rules still apply.
This first recorded quote can be up to one second after the touch on Hyperliquid
and up to half a second on Binance and Bybit. If the gap in quote history exceeds
the venue's limit, the order uses ordinary current-quote execution.
Limit order example
bash theme={null}
curl https://developers.myfundedperpetuals.com/v1/orders
-X POST
-H "Authorization: Bearer $FP_API_KEY"
-H "Content-Type: application/json"
-H "Idempotency-Key: $(uuidgen)"
-d '{
parent with GET /v1/twap-orders/{id}, and stop future slices with DELETE on
that resource. An in-flight child may still settle after cancellation begins.
Retain the parent ID returned at creation to inspect that schedule directly
throughout its lifecycle.
Scaled orders
Create a ladder with POST /v1/scaled-orders. Provide a start price, end
price, 2 to 10 rungs, and a flat, ascending, or descending distribution.
Every rung is an ordinary limit order and independently follows the platform's
fill and trading rules.
GET /v1/scaled-orders/{id} returns every rung's price, size, child order ID,
and placement rejection when applicable. DELETE fences unplaced rungs and
cancels every working child.
Reconcile fills and closed positions
GET /v1/fills?account_id=... returns filled orders in settlement order with
fees, realized P\&L, notional, liquidity role, and partial-fill lineage. Use
GET /v1/positions?account_id=...&status=closed for cursor-paginated closed
position records.
Treat all cursors as opaque. Order and strategy state can continue changing
after a response, so reconcile by resource ID until it reaches a terminal
status.
Track evaluation progress
GET /v1/accounts/{account_id} returns a risk snapshot with equity, loss-limit room,
and the profit still needed to pass. An evaluation passes when equity,
including unrealized P\&L, reaches the profit target, so track
After Nov 2, 2026
cap. The quote's reference_price, reference_kind, and reference_time
identify its execution reference. An estimate does not reserve a price.
Conditional trigger policy
New TP/SL and other conditional orders use Last Price on Binance, Bybit and
Hyperliquid. This is selected by the server; no new request parameter is
required. An external condition follows its trigger
market's source, while execution uses its order market's book.
Existing orders keep their original trigger policy when their price or size is
modified. Canceling and replacing an order adopts the current policy. Copied
orders, partial fills and attached TP/SL inherit the originating order's policy,
including when they are created after this update. A trigger does not guarantee
its fill price. See TP/SL behavior.
+ Eligible protective stop-market and take-profit market orders can fill from the
+ first recorded bid or ask at or after their touch. The accepted price stays fixed
+ during processing. When the touch spread is wider than the slippage cap, the
+ order fills at the touch bid (sell) or ask (buy), which can be further from the
+ touch midpoint than the cap; see
+ How triggered Stop Loss and Take Profit exits fill.
+ Recent order or position changes, unavailable quote history, or a touch price
+ beyond the order's slippage tolerance retain ordinary current-quote execution. Fees,
funding charges, loss limits, and liquidation rules still apply.
This first recorded quote can be up to one second after the touch on Hyperliquid
and up to half a second on Binance and Bybit. If the gap in quote history exceeds
the venue's limit, the order uses ordinary current-quote execution.
Limit order example
bash theme={null}
curl https://developers.myfundedperpetuals.com/v1/orders
-X POST
-H "Authorization: Bearer $FP_API_KEY"
-H "Content-Type: application/json"
-H "Idempotency-Key: $(uuidgen)"
-d '{
parent with GET /v1/twap-orders/{id}, and stop future slices with DELETE on
that resource. An in-flight child may still settle after cancellation begins.
Retain the parent ID returned at creation to inspect that schedule directly
throughout its lifecycle.
Scaled orders
Create a ladder with POST /v1/scaled-orders. Provide a start price, end
price, 2 to 10 rungs, and a flat, ascending, or descending distribution.
Every rung is an ordinary limit order and independently follows the platform's
fill and trading rules.
GET /v1/scaled-orders/{id} returns every rung's price, size, child order ID,
and placement rejection when applicable. DELETE fences unplaced rungs and
cancels every working child.
+ Price alerts
+ Price alerts are the same alerts you set on the trading chart. An alert
+ notifies you once when a market's mark price reaches your level. It never
+ places or changes an order.
+ Create one with POST /v1/price-alerts:
+ bash theme={null}
+ curl -X POST https://developers.myfundedperpetuals.com/v1/price-alerts
+ -H "Authorization: Bearer $FP_API_KEY"
+ -H "Content-Type: application/json"
+ -d '{"market_id":"binance|BTCUSDT","price":120000,"note":"breakout"}'
+ - The server reads the current mark and sets condition for you: above when
+ the level is above the mark, below when it is below.
+ - A fired alert appears in your notification center and sends a browser push
+ if you turned on push notifications. Your
+ account stream also receives a
+ price_alert event, so a bot can react without polling.
+ - Alerts belong to you, not to an account. Every API key you own, including
+ read-only keys and keys limited to certain accounts, sees and manages the
+ same alerts as the website.
+ - You can hold up to 25 armed alerts across the website and the API. Delete
+ one or wait for one to fire before arming another.
+ - PATCH /v1/price-alerts/{id} moves an armed alert to a new price or
+ note, choosing the direction again from the current mark.
+ - A triggered alert stays listed for 90 days. Re-arm it at the same price with
+ POST /v1/price-alerts/{id}/rearm, or remove it with DELETE.
Reconcile fills and closed positions
GET /v1/fills?account_id=... returns filled orders in settlement order with
fees, realized P\&L, notional, liquidity role, and partial-fill lineage. Use
GET /v1/positions?account_id=...&status=closed for cursor-paginated closed
position records.
Treat all cursors as opaque. Order and strategy state can continue changing
after a response, so reconcile by resource ID until it reaches a terminal
status.
Track evaluation progress
GET /v1/accounts/{account_id} returns a risk snapshot with equity, loss-limit room,
and the profit still needed to pass. An evaluation passes when equity,
including unrealized P\&L, reaches the profit target, so track
cap. The quote's reference_price, reference_kind, and reference_time
identify its execution reference. An estimate does not reserve a price.
Conditional trigger policy
New TP/SL and other conditional orders use Last Price on Binance, Bybit and
Hyperliquid. This is selected by the server; no new request parameter is
required. An external condition follows its trigger
market's source, while execution uses its order market's book.
Existing orders keep their original trigger policy when their price or size is
modified. Canceling and replacing an order adopts the current policy. Copied
orders, partial fills and attached TP/SL inherit the originating order's policy,
including when they are created after this update. A trigger does not guarantee
its fill price. See TP/SL behavior.
− Eligible protective stop-market and take-profit market orders can use the first
− recorded bid or ask at or after their touch. The accepted price stays fixed during
− processing. Recent order or position changes, unavailable quote history, or a
− spread outside the slippage cap retain ordinary current-quote execution. Fees,
+ Eligible protective stop-market and take-profit market orders can fill from the
+ first recorded bid or ask at or after their touch. The accepted price stays fixed
+ during processing. When the touch spread is wider than the slippage cap, the
+ order fills at the touch bid (sell) or ask (buy), which can be further from the
+ touch midpoint than the cap; see
+ How triggered Stop Loss and Take Profit exits fill.
+ Recent order or position changes, unavailable quote history, or a touch price
+ beyond the order's slippage tolerance retain ordinary current-quote execution. Fees,
funding charges, loss limits, and liquidation rules still apply.
This first recorded quote can be up to one second after the touch on Hyperliquid
and up to half a second on Binance and Bybit. If the gap in quote history exceeds
the venue's limit, the order uses ordinary current-quote execution.
Limit order example
bash theme={null}
curl https://developers.myfundedperpetuals.com/v1/orders
-X POST
-H "Authorization: Bearer $FP_API_KEY"
-H "Content-Type: application/json"
-H "Idempotency-Key: $(uuidgen)"
-d '{
parent with GET /v1/twap-orders/{id}, and stop future slices with DELETE on
that resource. An in-flight child may still settle after cancellation begins.
Retain the parent ID returned at creation to inspect that schedule directly
throughout its lifecycle.
Scaled orders
Create a ladder with POST /v1/scaled-orders. Provide a start price, end
price, 2 to 10 rungs, and a flat, ascending, or descending distribution.
Every rung is an ordinary limit order and independently follows the platform's
fill and trading rules.
GET /v1/scaled-orders/{id} returns every rung's price, size, child order ID,
and placement rejection when applicable. DELETE fences unplaced rungs and
cancels every working child.
+ Price alerts
+ Price alerts are the same alerts you set on the trading chart. An alert
+ notifies you once when a market's mark price reaches your level. It never
+ places or changes an order.
+ Create one with POST /v1/price-alerts:
+ bash theme={null}
+ curl -X POST https://developers.myfundedperpetuals.com/v1/price-alerts
+ -H "Authorization: Bearer $FP_API_KEY"
+ -H "Content-Type: application/json"
+ -d '{"market_id":"binance|BTCUSDT","price":120000,"note":"breakout"}'
+ - The server reads the current mark and sets condition for you: above when
+ the level is above the mark, below when it is below.
+ - A fired alert appears in your notification center and sends a browser push
+ if you turned on push notifications. Your
+ account stream also receives a
+ price_alert event, so a bot can react without polling.
+ - Alerts belong to you, not to an account. Every API key you own, including
+ read-only keys and keys limited to certain accounts, sees and manages the
+ same alerts as the website.
+ - You can hold up to 25 armed alerts across the website and the API. Delete
+ one or wait for one to fire before arming another.
+ - PATCH /v1/price-alerts/{id} moves an armed alert to a new price or
+ note, choosing the direction again from the current mark.
+ - A triggered alert stays listed for 90 days. Re-arm it at the same price with
+ POST /v1/price-alerts/{id}/rearm, or remove it with DELETE.
Reconcile fills and closed positions
GET /v1/fills?account_id=... returns filled orders in settlement order with
fees, realized P\&L, notional, liquidity role, and partial-fill lineage. Use
GET /v1/positions?account_id=...&status=closed for cursor-paginated closed
position records.
Treat all cursors as opaque. Order and strategy state can continue changing
after a response, so reconcile by resource ID until it reaches a terminal
status.
Track evaluation progress
GET /v1/accounts/{account_id} returns a risk snapshot with equity, loss-limit room,
and the profit still needed to pass. An evaluation passes when equity,
including unrealized P\&L, reaches the profit target, so track