# WebHooks / API Autotrading

Blazing App allows you to automate your trading through its webhook API integration. This feature enables you to connect your custom buy templates with external systems, providing seamless and automated trading. Below is a step-by-step guide to setting up and using Blazing Webhooks: ## Webhooks {% hint style="success" %} Webhooks work for all Blazing supported Chains and Dexes {% endhint %} {% content-ref url="../supported-chains-and-dexes" %} [supported-chains-and-dexes](https://blazingapp.gitbook.io/tutorials/supported-chains-and-dexes) {% endcontent-ref %} {% hint style="info" %} In order to access and setup webhooks it is required that you have account registered with Blazing. {% endhint %} ## Webhooks Benchmark {% file src="" %}

SOLANA TRADING PLATFORM BENCHMARK REPORT

BENCHMARK WINNER: Blazing
Performance: 9/10 wins (90% success rate)

Executive Summary

This comprehensive benchmark evaluated three leading Solana trading platforms across 10 rounds of 0.001 SOL trades. The analysis focuses on blockchain landing performance - the actual order transactions appear on the Solana blockchain. **Key Findings:** * Blazing achieved superior performance with 9 blockchain wins (90%) * 0 rounds required same-slot scenario analysis using block position data * All platforms maintained 100% transaction success rate with zero failures * Block position analysis provided accurate winner determination for same-slot scenarios

Detailed Round-by-Round Analysis

Round 1 Results:

* Winner: Blazing * Second Place: Jupiter * Third Place: GMGN * Slot Numbers: Blazing: 354176080, Jupiter: 354176083, GMGN: 354176084 **Transaction Hashes:** * Blazing: 4ByGihRQTYjp...AvePAV6w3DEW * Jupiter: 2wEjYB5KeV6C...E5RhjmvR58Si * GMGN: 3y6SKrnrRYpb...NGjkbc8cMKPR

Round 2 Results:

• Winner: Blazing • Second Place: GMGN • Third Place: Jupiter • Slot Numbers: 1. Blazing: 354176098, 2. Jupiter: 354176100, 3. GMGN: 354176099 **Transaction Hashes:** * Blazing: 58ukmtx3mVqr...EAwFKG5qdb2j * Jupiter: 3r7wLLA6hTSg...fHMwcRE6xu1x * GMGN: 2YnuyUqnS8h3...n9uGFoYLVqNR

Round 3 Results:

• Winner: Jupiter • Second Place: Blazing • Third Place: GMGN • Slot Numbers: 1. Blazing: 354176116, 2. Jupiter: 354176116, 3. GMGN: 354176116 **Transaction Hashes:** * Blazing: 39hpcMEVCyZ2...GzNTUqKqWiP2 * Jupiter: 5rSAJEdw9L4G...jjHWhAdSgt36 * GMGN: 3nrfpsYG18yE...GXyi1TpzGJ99 * Same-Slot Analysis: \ Slot 354176116 — Jupiter → Blazing → GMGN

Round 4 Results:

• Winner: Blazing • Second Place: GMGN • Third Place: Jupiter **Slot Numbers:** 1. Blazing: 354176157, 2. Jupiter: 354176161, 3. GMGN: 354176158 **Transaction Hashes:** * Blazing: 2ZB9JMUsGQBw\...ptXm3X8u7CLe * Jupiter: 3k7gktcqZjQy...mW8zSL1hFYyL * GMGN: 4T3MkPb2rTyg...dSmSCzLMBf2E

Round 5 Results:

• Winner: Blazing • Second Place: Jupiter • Third Place: GMGN • Slot Numbers: 1. Blazing: 354176175, 2. Jupiter: 354176176, 3. GMGN: 354176176 **Transaction Hashes:** * Blazing: 5n5R3HSmSkq5...TuGUXAWiDE7D * Jupiter: PtgqpPKpEfjK...nxvScEQsFv1c * GMGN: 4o6aDnZzS5uh...Aa2gZ9Jkp8nu * Same-Slot Analysis: \ Slot 354176176 - Jupiter → GMGN

Round 6 Results:

• Winner: Blazing • Second Place: GMGN • Third Place: Jupiter **Slot Numbers:** 1. Blazing: 354176227, 2. Jupiter: 354176232, 3. GMGN: 354176228 **Transaction Hashes:** * Blazing: 5vww3UTuVRdM...RBW2DT75Dbyj * Jupiter: 3fEzuBHfqfMj...feAR6qqH4RHE * GMGN: 28Xh8pVpDSCk...jjK44KrCdKt9

Round 7 Results:

• Winner: Blazing • Second Place: GMGN • Third Place: Jupiter Slot Numbers: 1. Blazing: 354176246, 2. Jupiter: 354176248, 3. GMGN: 354176246 Transaction Hashes: * Blazing: 2bEZLorjdhhH...BBuHZ4Wizxut * Jupiter: 649hsJ5gRqz6...eY8jBXGzySFo * GMGN: Mj8r4sdDMYwP...VLYyp5AqS8Xt * Same-Slot Analysis: Slot 354176246 - Blazing → GMGN

Round 8 Results:

* Winner: Blazing * Second Place: GMGN * Third Place: Jupiter **Slot Numbers:** 1. Blazing: 354176296, 2. Jupiter: 354176298, 3. GMGN: 354176297 **Transaction Hashes:** * Blazing: 2oPPyoQsyYiT...BA8aE9j65Uoa * Jupiter: 2mNreMfaNnA5...bqNwueMeXHY9 * GMGN: 4Z4qU6bcd5a3...k5GrFKBR9rag

Round 9 Results:

• Winner: Blazing • Second Place: GMGN • Third Place: Jupiter **Slot Numbers:** 1. Blazing: 354176314, 2. Jupiter: 354176316, 3. GMGN: 354176314 **Transaction Hashes:** * Blazing: nyAj1JuvXih8...yjaEE37451Ve * Jupiter: 37VXzR1BvFcj...RNJTESb2Y3Hv * GMGN: 5GqS9cTi1xS3...dqE9555k4trL **Same-Slot Analysis:** \ Slot 354176314 - Blazing → GMGN

Round 10 Results:

• Winner: Blazing • Second Place: GMGN • Third Place: Jupiter **Slot Numbers:** 1. Blazing: 354176356, 2. Jupiter: 354176360, 3. GMGN: 354176357 **Transaction Hashes:** * Blazing: 22PcyiJeeoqz...YXJToKJKvRPd * Jupiter: 5pKi9pkvEjqp...VkGq4ueUxF1o * GMGN: 4zhPiDkhbobC...QFFKErgDW4Ad

Platform Performance Summary

**Overall Performance Rankings:** 1. Blazing - Top Performer * Blockchain Wins: 9/10 (90%) * Success Rate: 100.0% * Average Ranking: 1.1
2. Jupiter * Blockchain Wins: 1/10 (10%) * Success Rate: 100.0% * Average Ranking: 2.6
3. GMGN * Blockchain Wins: 0/10 (0%) * Success Rate: 100.0% * Average Ranking: 2.3

Same-Slot Scenario Analysis

**Block Position Methodology:** \ When multiple transactions are confirmed within the same Solana slot, the winner is determined by analyzing their exact position within that block. Our analysis utilizes the Helius API to fetch block data and determine the canonical transaction order. \ \ **Same-Slot Scenarios Identified:** \ \ • Round 3, Slot 354176116: Jupiter → Blazing → GMGN • Round 5, Slot 354176176: Jupiter → GMGN • Round 7, Slot 354176246: Blazing → GMGN • Round 9, Slot 354176314: Blazing → GMGN

Methodology

**Blockchain Winner Determination Process:** 1. Slot Comparison: Platform with the lowest confirmed slot number is ranked first 2. Block Position Analysis (same slot): Exact transaction order within the block determined using Helius API 3. Blockchain Ranking: Final ranking based on confirmed blockchain landing order **Block Position Analysis Methodology:** When multiple platforms confirm transactions within the same slot, we utilize the Helius API to fetch comprehensive block data and determine the exact transaction order. This methodology provides the most accurate determination of which transaction was confirmed first on the blockchain, ensuring precise performance measurement. **Testing Parameters:** • Trade Amount: 0.001 SOL per transaction • Test Rounds: 10 comprehensive rounds • Success Rate Measurement: 100% transaction confirmation required • Block Position Verification: Helius API integration for same-slot scenarios • Token Tested: 5v2wpT6fA97hTeHXwX4oDzoFog344ShBYrf2zWivpump ## Conclusion This comprehensive benchmark reveals that Blazing consistently outperforms competitors in blockchain landing speed, winning 9 out of 10 rounds (90% win rate). **Key Insights:** \ \ • Blazing demonstrates superior blockchain landing performance with consistent first-place finishes • Block position analysis provides accurate same-slot winner determination when multiple transactions confirm in the same slot • All platforms maintain 100% reliability with zero transaction failures • Performance differences are measurable and consistent across all 10 benchmark rounds • Same-slot scenarios demonstrate the importance of precise block position analysis for accurate performance measurement **Recommendation:** \ For applications requiring optimal blockchain landing speed and consistent performance, **Blazing** is the recommended choice based on this comprehensive analysis. The platform's superior blockchain landing performance makes it ideal for time-sensitive trading applications where transaction confirmation order is critical.

## How to create a Webhook {% tabs %} {% tab title="Telegram Bot" %} 1. **Create a Template** In [Blazing Tg bot](https://t.me/blazing_trading_bot) - head to Settings → Templates → Create template

Additional information on each parameter when configuring the template: {% content-ref url="../telegram-bot/settings/templates" %} [templates](https://blazingapp.gitbook.io/tutorials/telegram-bot/settings/templates) {% endcontent-ref %}

After successfully creating the template, you will be able to see it in the list.

2. **Create a webhook for a Template.** Head back to Settings → Webhooks settings.

Click Create Webhook

Select a Template to use with Webhook

{% hint style="info" %} After successful Webhook creation, you will receive the webhook URL and access token that should be used when calling the specific webhook. {% endhint %} `Webhook URL:` [`https://blazingworld.me/api/v1/order/webhook/3eab2772-1f3c-42f9-bc70-6c3a79c469bc/trigger/buy?b=8&l=en`](https://blazingworld.me/api/v1/order/webhook/3eab2772-1f3c-42f9-bc70-6c3a79c469bc/trigger/buy?b=8\&l=en)

{% endtab %} {% tab title="WebApp" %} 1. **Create a Template** Open left side menu → Template management

Click Add New Template

Configure your Template. Find all settings descriptions here: {% content-ref url="templates" %} [templates](https://blazingapp.gitbook.io/tutorials/webapp/templates) {% endcontent-ref %} {% hint style="info" %} Once your Template is saved, go back to Templates Management and create a Webhook {% endhint %}

Name your Webhook and select a Template that will be used for it.

Copy & Save your Webhook URL and Access Token.

{% hint style="warning" %} Do not share your Access token with the public or 3rd party persons. {% endhint %} {% endtab %} {% endtabs %} ## Managing Webhooks To manage or update your webhooks, navigate to Settings -> Devices & Webhooks. {% hint style="info" %} Here, you can select a different template to be used with the webhook if needed. {% endhint %}

## **Interact with Webhook** To trigger the webhook, send a `POST` request to the **Webhook URL** with the **Access Token** included as a bearer token in the headers. The endpoint requires one parameter in the request body: the contract address of the token. | **Header** | **Value** | | ------------- | --------------------------------------------------------------------- | | Content-Type | `application/json` | | Accept | `application/json` | | Authorization | `Bearer ` | | Origin | [`https://webhook.blazingworld.me`](https://webhook.blazingworld.me/) | | User-Agent | BlazingBot/1.0 | ### JSON Body The body must contain a single parameter:

Parameter	Type	Description
contract	string	The on-chain contract address of the token.
retry_blocks	integer (optional)	Number of blocks to retry the transaction (1-100). Default: 1.
affiliate	string (optional)	Referral identifier (usually a username). For new users, it works like a sticky referral. For existing users, it can be applied on a per-transaction basis.
idempotency_key	string (optional)	Unique request ID to prevent duplicate execution. If the same webhook is sent multiple times with the same idempotency_key, it will only be processed once.

#### **Example Request (curl)** ```json curl -X POST 'https://blazingworld.me/api/v1/order/webhook/d3554524-453d-4d85-9a04-d78bc539a2f7/trigger/buy?b=8&l=en' \ -H 'Content-Type: application/json' \ -H 'Accept: application/json' \ -H 'Authorization: Bearer ' \ -H 'Origin: https://webhook.blazingworld.me' \ -H 'User-Agent: BlazingBot/1.0' \ -d '{ "contract": "0xabc123...", "retry_blocks": 10, "affiliate": "username", "idempotency_key": "any_string" }' ``` #### **Key Notes** * For `retry_blocks` Value must be between 1 and 100. Higher values increase chance of transaction landing on-chain during congestion . Default is 1, when not specified. * The `user-session-id` is embedded in the URL. Do **not** include it as a header. * The `contract` field must be a valid on-chain token address (e.g. `0xabc123...`). * Ensure all headers and the JSON body are set correctly — otherwise, the webhook will fail. ## Webhooks use case with DRBT bot {% embed url="" %}

Using Webhooks with DRBT

[De-Fi Robot](https://portal.defirobot.org/) is a Platform that provides configurable alpha bots, allowing you to set up different settings for catching new launches. Check the [demo video](https://youtu.be/0LasMsUz96w). ### 1. Connect the Webhook to the DRBT Bot Now we’ll link the webhook to the DRBT bot: 1. Copy the Webhook URL from the Blazing WebApp.

2. Open the DRBT Filters Bot and select the query where you want to connect the webhook. 3. Click ‘*Webhook*’ and paste the Webhook URL.

4. Optionally, edit the query settings or rename the query for easier identification. ### 2. Activate Auto-Buy and Link Your Access Token 1. In the DRBT bot, click ‘Auto Buy’ and select ‘Blazing’.

2. Go back to the Blazing WebApp and copy your Access Token.

3. Return to the DRBT bot and reply with the Access Token to finalize the connection.

Once everything is configured, you should see the Webhook URL listed and a green check next to the ‘Sniper Key’ in the DRBT bot. ### 3. Monitoring and Confirmation

Once a call comes through: * You’ll receive a notification from the Blazing Telegram Bot when a call is triggered and the buy is executed. * You can check the token that was bought on the WebApp. #### Tracking Your Recent Buys

* Navigate to the Profit & Loss (PnL) panel in the WebApp to track your recent buys. * You can also instantly share your PnL card before selling for easy updates.