--- title: "List Trades" method: GET path: "/v1/trades/{symbol}" tags: ["Market Data"] --- # List Trades `GET /v1/trades/{symbol}` ## Request - Base URL: `https://api.gemini.com` - URL: `https://api.gemini.com/v1/trades/{symbol}` - Auth: none declared This will return the trades that have executed since the specified timestamp. Timestamps are either seconds or milliseconds since the epoch (1970-01-01). See the [Data Types](/data-types) section about `timestamp` for information on this. Each request will show at most 500 records. If no `since` or `timestamp` is specified, then it will show the most recent trades; otherwise, it will show the most recent trades that occurred after that timestamp. ## Path parameters - `symbol` string, required ## Query parameters - `timestamp` union: timestamp - string: Gemini strongly recommends using milliseconds instead of seconds for timestamps. | Timestamp format | Example | Supported request type | |-----------------------|-----------------------|------------------------| | string (seconds) | `1495127793` | `POST` only | | string (milliseconds) | `1495127793000` | `POST` only | - integer: Gemini strongly recommends using milliseconds instead of seconds for timestamps. | Timestamp format | Example | Supported request type | |-----------------------------|---------------------------|------------------------| | whole number (seconds) | `1495127793` | `GET`, `POST` | | whole number (milliseconds) | `1495127793000` | `GET`, `POST` | - `since_tid` number - `limit_trades` number - `include_breaks` boolean ## Response `200` The response will be an array of JSON objects, sorted by timestamp, with the newest trade shown first. - Trade[] - `timestamp` union: timestamp - string: Gemini strongly recommends using milliseconds instead of seconds for timestamps. | Timestamp format | Example | Supported request type | |-----------------------|-----------------------|------------------------| | string (seconds) | `1495127793` | `POST` only | | string (milliseconds) | `1495127793000` | `POST` only | - integer: Gemini strongly recommends using milliseconds instead of seconds for timestamps. | Timestamp format | Example | Supported request type | |-----------------------------|---------------------------|------------------------| | whole number (seconds) | `1495127793` | `GET`, `POST` | | whole number (milliseconds) | `1495127793000` | `GET`, `POST` | - `timestampms` union: timestamp - string: Gemini strongly recommends using milliseconds instead of seconds for timestamps. | Timestamp format | Example | Supported request type | |-----------------------|-----------------------|------------------------| | string (seconds) | `1495127793` | `POST` only | | string (milliseconds) | `1495127793000` | `POST` only | - integer: Gemini strongly recommends using milliseconds instead of seconds for timestamps. | Timestamp format | Example | Supported request type | |-----------------------------|---------------------------|------------------------| | whole number (seconds) | `1495127793` | `GET`, `POST` | | whole number (milliseconds) | `1495127793000` | `GET`, `POST` | - `tid` integer: The trade ID number - `price` string, decimal: The price the trade was executed at - `amount` string, decimal: The amount that was traded - `exchange` string: Will always be "gemini" - `type` 'buy' | 'sell': - `buy` means that an ask was removed from the book by an incoming buy order. - `sell` means that a bid was removed from the book by an incoming sell order. - `broken` boolean: Whether the trade was broken or not. Broken trades will not be displayed by default; use the `include_breaks` to display them. ## Other responses - `400`: Bad request - malformed request or invalid parameters - `404`: Resource not found - `429`: Too many requests - you have exceeded the rate limit - `500`: Internal server error --- [API](https://skmtc.dev/gemini/apis/rest-api.md) - [All operations](https://skmtc.dev/gemini/apis/rest-api/llms.txt) - [OpenAPI document](https://skmtc.dev/gemini/apis/rest-api/revisions/24979792d748?raw)