Snaxpot
Snaxpot lottery actions are available under POST /v1/trade. All actions require EIP-712 authentication scoped to a subaccount.
Endpoint
POST https://papi.synthetix.io/v1/tradeAvailable Actions
| Action | Type | Description |
|---|---|---|
| Get Snaxpot Epoch Tickets | Query | Retrieve lottery tickets and epoch statistics across an epoch range |
| Get Snaxpot My Winning Tickets | Query | Retrieve winning tickets for a resolved epoch |
clearSnaxpotPreference | Write | Clear the subaccount's Snaxpot number preference |
saveSnaxpotTickets | Write | Save Snaxpot ticket selections for the current epoch |
setSnaxpotPreference | Write | Set the subaccount's Snaxpot number preference |
Authentication
| Action | Owner signature | Delegated signer |
|---|---|---|
getSnaxpotEpochTickets | Yes | Yes |
getSnaxpotMyWinningTickets | Yes | Yes |
clearSnaxpotPreference | Yes | Yes |
saveSnaxpotTickets | Yes | Yes |
setSnaxpotPreference | Yes | Yes |
Delegated signers with appropriate permissions can manage Snaxpot preferences and tickets on behalf of a subaccount without requiring the owner's private key for each transaction. Previously, clearSnaxpotPreference, saveSnaxpotTickets, and setSnaxpotPreference required owner-only signatures.
Query actions use SubAccountAction EIP-712 signing. Write actions use action-specific EIP-712 typed data with nonce and optional expiresAfter at the request root, consistent with other trade write endpoints.
Related Endpoints
- Get Snaxpot Epoch Tickets — Query tickets and epoch statistics
- Get Snaxpot My Winning Tickets — Query winning tickets for a resolved epoch
- Add Delegated Signer — Grant delegation permissions to a bot or operator wallet