> For the complete documentation index, see [llms.txt](https://docs.sigrex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sigrex.io/more/browser-extension.md).
# Browser Extension
The Sigrex Chrome Extension lets you send trading signals to your bots instantly, without leaving your browser.
Install Extension: [Chrome Web Store](https://chromewebstore.google.com/detail/towerflow/booenncomgienhnfhjgmcbmeogfhhbmc)
After a quick authentication, you can trigger **BUY / SELL** actions to your **own bot webhooks**, exactly the same way as sending a Manual Signal from the Sigrex platform — but faster and always accessible.
***
### 🚀 What Is the Chrome Extension?
The extension is a lightweight interface for discretionary and hybrid trading workflows. It enables you to:
* Send manual trading signals from anywhere on the web
* Execute trades without opening the Sigrex dashboard
* Use the same webhook-based execution pipeline as the platform
There is **no difference** in how signals are processed — only in how fast you can send them.
***
### 🔐 Authentication
On first use:
1. Open the extension
2. Authenticate with your Sigrex account
3. Your active bot webhooks are securely synced
Authentication tokens are scoped and revocable. No sensitive credentials are stored in plaintext.
***
### 🧩 Sending a Trading Signal
The extension UI mirrors the Manual Signal interface in Sigrex.
#### Required Fields
**Webhook**
Select one of your active bot webhooks.
Only webhooks you own or have access to will be listed.
***
**Symbol**
Trading pair or instrument.
**Example:**
```
BTCUSDT
```
***
**Order Side**
Choose the trade direction:
* **BUY** – Open or add to a long position
* **SELL** – Close or open a short position (depending on bot logic)
***
### ⚙️ Optional Parameters
Optional parameters allow you to refine how the trade is executed.\
If a field is set to `0`, it is ignored and the bot’s default logic applies.
***
#### Amount
Defines the trade size.
* Interpreted according to your bot and exchange configuration
* Can represent base or quote amount depending on setup
**Example:**
```
Amount: 0.05
```
***
#### 📌 Important Notes
* All optional parameters are forwarded **exactly as provided**
* Validation and execution behavior depend on the receiving bot
* Parameters behave identically to Manual Signals sent from the Sigrex platform
***
### ⚙️ How It Works
When you send a signal:
1. The extension submits the signal to Sigrex
2. Sigrex forwards it to the selected webhook
3. All connected bots receive and process the signal in real time
This ensures:
* Consistent execution
* Unified logging
* Identical behavior across platform, extension, and API usage
***
### 🧠 Common Use Cases
* Quickly react to market moves while browsing charts
* Combine manual discretion with automated execution
* Trigger trades during research, calls, or live sessions
* Test webhook setups without opening the dashboard
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sigrex.io/more/browser-extension.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
