# SUBSCRIBE Trades
**REQUEST**
```
|
* \*data\*\* array of strings required
Channel name in the format `trades:ASSET` or `trades:INSTRUMENT_NAME`. Eg. `trades:ETH` or `trades:ETH-31MAR23-1350-C`
|
```
|
|---|
</th>
</tr>
|
| * \*op\*\* string required Operation code allowed values: `subscribe` `unsubscribe` |
* `ASSET` allowed values: `ETH`
Example
```json
{
"op":"subscribe",
"data": ["trades:ETH-31MAR23-1350-C"]
}
```
**RESPONSE**
```
|
data.**trade\_id** string required
Trade transaction hash. Eg. `0x17897e438f15c459a3a4ed44687dc7f0c4c678b2b005ea87bbae35346f279f02`
|
|
data.**instrument\_id** string required
Instrument ID number. Eg. `12`
|
|
data.**instrument\_name** string required
Instrument name. Eg.` ETH-24DEC22-1250-C`
|
|
data.**instrument\_type** string required
Type of instrument. Allowed values: `OPTION` `PERPETUAL`
|
|
data.**side** object required
Trade side. Allowed values: `buy` `sell`
|
|
data.**price** object required
Price in USD. Eg. `12.23`
|
|
data.**amount** string
Amount of contracts. Eg. `10.4`
|
|
data.**created\_timestamp** string required
Timestamp in UNIX timestamp in nanoseconds. Eg. `1680249600000000000`
|
```
|
|---|
</th>
</tr>
|
| * \*channel\*\* string required Channel name in the format `index:ASSET`. Eg. `index:ETH` |
Example
```json
{
"channel": "trades:ETH-20JAN23-1200-P",
"data": {
"trade_id": "0x17897e438f15c459a3a4ed44687dc7f0c4c678b2b005ea87bbae35346f279f02",
"instrument_id": 830,
"instrument_name": "ETH-20JAN23-1200-P",
"instrument_type": "OPTION",
"side": "sell",
"price": "0.58",
"amount": "1",
"created_ttimestamp": "1674118637229190091"
}
}
```
---
# Agent Instructions: 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:
```
GET https://docs.aevo.xyz/api-reference/websocket-api/public-operations/subcribe-trades.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.