> For the complete documentation index, see [llms.txt](https://docs.boba.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.boba.xyz/agents/boba-agents/core-capabilities/perpetuals-trading/trade-history.md).

# Trade History

***

### Overview

Trade history is your full log of every order that has executed. While Fills & PnL focuses on performance analysis, Trade History is your raw execution record: what you traded, when, at what price, and what you paid.

**What you can do:**

* View all recent trade executions
* Filter by asset, time range, or direction
* See exact execution prices and fees for every fill
* Track how orders were filled (full or partial)
* Export or review your trading activity

***

### Viewing Trade History

| Prompt                               | Interpretation             |
| ------------------------------------ | -------------------------- |
| "Show my trade history"              | All recent executed trades |
| "What trades have I made?"           | Full execution log         |
| "Show my recent trades"              | Most recent fills          |
| "My trading activity today"          | Today's executions only    |
| "Show everything I traded this week" | Past 7 days of fills       |

***

### Filtering by Asset

| Prompt                         | Interpretation               |
| ------------------------------ | ---------------------------- |
| "Show my BTC trade history"    | All BTC executions           |
| "What ETH trades have I made?" | ETH-specific fills           |
| "SOL trading history"          | All SOL executions           |
| "Have I traded DOGE recently?" | Checks for recent DOGE fills |
| "Show all my altcoin trades"   | Filters to non-BTC/ETH fills |

***

### Filtering by Time

You can query trades from any time range using natural language. The agent converts your timeframe automatically.

| Prompt                          | Interpretation            |
| ------------------------------- | ------------------------- |
| "Trades from the last 24 hours" | Past day of executions    |
| "What did I trade yesterday?"   | Yesterday's fills         |
| "Show my trades from last week" | Past 7 days               |
| "Trading history for February"  | All fills in February     |
| "Trades since Monday"           | Start of the current week |
| "My fills from the last hour"   | Very recent executions    |

***

### Filtering by Direction

| Prompt                                  | Interpretation                        |
| --------------------------------------- | ------------------------------------- |
| "Show all my longs"                     | Fills where direction was Open Long   |
| "What shorts have I opened?"            | Open Short fills                      |
| "Show my closed trades"                 | Close Long and Close Short fills      |
| "When did I last close a BTC position?" | Most recent BTC close fill            |
| "How many trades have I opened today?"  | Count of Open Long + Open Short fills |

***

### Understanding Fill Details

Each trade in your history includes:

| Field          | What It Shows                                               |
| -------------- | ----------------------------------------------------------- |
| **Asset**      | Token traded                                                |
| **Side**       | Buy or Sell                                                 |
| **Direction**  | Open Long, Open Short, Close Long, Close Short              |
| **Price**      | Exact execution price                                       |
| **Size**       | Quantity in contract units                                  |
| **Notional**   | USD value of the trade                                      |
| **Fee**        | Fee paid or rebate earned                                   |
| **Order Type** | How the order was placed (Market, Limit, Stop-Market, etc.) |
| **Time**       | Exact timestamp of execution                                |

#### Reading Direction vs Side

The combination of side and direction tells you exactly what happened:

| Side | Direction   | What Happened               |
| ---- | ----------- | --------------------------- |
| Buy  | Open Long   | Opened a new long position  |
| Sell | Open Short  | Opened a new short position |
| Sell | Close Long  | Closed an existing long     |
| Buy  | Close Short | Closed an existing short    |

***

### Partial Fills

Some orders fill in multiple parts, especially limit orders on less liquid assets. Each partial fill appears as a separate entry in your trade history.

**Example**: You place a $5,000 limit buy on an altcoin perp. It fills in three chunks:

| Fill   | Price  | Notional | Fee             |
| ------ | ------ | -------- | --------------- |
| Fill 1 | $2.450 | $2,000   | -$0.20 (rebate) |
| Fill 2 | $2.450 | $1,500   | -$0.15 (rebate) |
| Fill 3 | $2.449 | $1,500   | -$0.15 (rebate) |

All three fills are part of the same order. Your position shows the weighted average entry price.

***

### Trade History vs Fills & PnL

These two pages serve different purposes:

|                         | Trade History                  | Fills & PnL                 |
| ----------------------- | ------------------------------ | --------------------------- |
| **Focus**               | Raw execution record           | Performance analysis        |
| **Shows**               | Every individual fill          | PnL, portfolio, fees        |
| **Best for**            | Auditing, verifying executions | Understanding profitability |
| **Question it answers** | "What exactly did I trade?"    | "How much did I make?"      |

Use Trade History to verify that your orders executed as expected. Use Fills & PnL to analyze whether your trading strategy is working.

***

### Common Workflows

#### Verifying an Execution

```
1. "Show my recent BTC trades"      → Find the specific fill
2. Check execution price             → Compare to what you expected
3. Check direction                    → Opened or closed?
```

#### Auditing a Trading Session

```
1. "Show my trades from today"       → See everything you did
2. Count opens vs closes              → Are you accumulating or reducing?
3. "Show my portfolio"                → Net result of the day
```

#### Investigating a Stop-Loss Trigger

```
1. "Show my recent ETH trades"       → Find the stop-loss fill
2. Check execution price              → How much slippage from trigger?
3. Check time                         → When exactly did it trigger?
4. Compare to candle data             → Was it a wick or sustained move?
```

***

### Pro Tips

1. **Review fills after volatile sessions** - Verify execution prices match your expectations
2. **Check for partial fills on limit orders** - Your average entry may differ from your limit price
3. **Watch fees on high-frequency trading** - Many small trades add up in fees quickly
4. **Compare stop-loss trigger vs fill price** - In fast markets, slippage between trigger and fill can be significant
5. **Use trade history for tax reporting** - Your fill log is the source of truth for cost basis and gains
6. **Spot patterns in your trading** - Are you opening more longs than shorts? Closing too early? The data tells the story

***


---

# 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.boba.xyz/agents/boba-agents/core-capabilities/perpetuals-trading/trade-history.md?ask=<question>&goal=<endgoal>
```

`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.
