route: "sanctum" (with sanctumKind and sanctum_order) forwards to Sanctum’s execute endpoint, which adds MEV protection and smarter retries. Use it when broadcasting transactions that came back from /stake or /unstake with route: "sanctum".
hubra_token is required on every call. Without a matching token, the endpoint rejects the request with 403 forbidden.Request
Response
When to use Sanctum routing
The simple rule: if the build response had
route: "sanctum", broadcast with route: "sanctum" and forward the Sanctum-specific fields.
Sanctum’s broadcaster adds MEV protection and smarter retries. Plain RPC works for any signed transaction; the chain itself does not distinguish.
Signing example (Node + @solana/web3.js)
sol-native-stake, tx.sign([wallet]) only fills the wallet’s slot. The stake-account slot is pre-signed by Hubra’s server.
Errors
See also
Hubra token
The HMAC mechanism in detail.
POST /stake
Build a stake transaction.
POST /unstake
Build an unstake transaction.
Errors
Problem-details and slugs.