Request Lifecycle Reference
A developer reference for CallPut asynchronous option requests, including submission, request keys, Pending, Executed and Cancelled states, close requests and settlement checks.
Submission
Submitting a transaction creates or advances a request workflow; it should not automatically be presented as a filled option.
Pending
While pending, dependent actions should wait or explicitly account for uncertainty.
Executed
After execution, query the resulting position state and relevant balances before presenting success.
Cancelled
A cancelled request should trigger a fresh market read before any retry.
Settlement
After expiry, use the documented settlement path and verify final state on the correct network.
Frequently asked questions
What does the Request Lifecycle Reference page cover?
It covers a developer reference for CallPut asynchronous option requests, including submission, request keys, Pending, Executed and Cancelled states, close requests and settlement checks.
Does a documentation example guarantee a live market or fill?
No. Market availability, expiries, strikes, liquidity, fees and contract state can change. Check the live application and selected network before acting.
Are CallPut stock and ETF options ownership of the referenced security?
No. The documented stock and ETF options are synthetic onchain instruments and do not grant shares, fund units, dividends, voting rights or physical delivery.