Integration guide

The Snipe API operates on an intent-based model. Imagine you’re a developer looking to integrate sniping capabilities into your wallet, Telegram bot, or other automated trading product.

There are two ways to setup intents: EIP 712 Intents (for non-custodial wallets) and Bot Intents (for telegram trading bots). The only difference between the two is how transactions are signed.

EIP712 Intents for Wallets

EIP712 Intents can be used to enable fully non-custodial sniping in non-custodial wallets. An optional notification can be sent to your servers in order to serve a push notification for successful or failed intents. You can try setting up a non-custodial intent on the OpenLaunch website.

Make sure the Snipe router is approved for spending the wrapped ETH of the sniping wallet. The API will return an error if no approval has been set.

EIP 712 sniping

Bot Intents for Telegram trading bots

Bot intents works similarly to EIP 712 intents. In this case, your API sets up an intent with the Snipe API, and responds to a webhook for transaction signature.

No Wrapped Eth approval required in this case.

Entire lifecycle of a successful sniping intent