> For the complete documentation index, see [llms.txt](https://docs.42.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.42.space/for-developers/rest-api-alpha/leaderboard/get-wallet-trading-stats.md).

# Get wallet trading stats

GET /api/v1/market-data/leaderboard/stats/{wallet\_address}

## Get wallet trading stats

> Returns lifetime aggregate trading statistics for a single wallet, including total PnL, win rates, buy/sell volumes, trade count, and best/worst individual trades. Total PnL is net of protocol and integrator fees; best/worst trade are single-row realised deltas and net only the integrator fee.

```json
{"openapi":"3.1.1","info":{"title":"FortyTwo Read API","version":"1.0"},"tags":[{"description":"GET /api/v1/market-data/leaderboard/stats/{wallet_address}","name":"get-wallet-stats"}],"servers":[{"url":"https://rest.ft.42.space/"}],"paths":{"/api/v1/market-data/leaderboard/stats/{wallet_address}":{"get":{"description":"Returns lifetime aggregate trading statistics for a single wallet, including total PnL, win rates, buy/sell volumes, trade count, and best/worst individual trades. Total PnL is net of protocol and integrator fees; best/worst trade are single-row realised deltas and net only the integrator fee.","tags":["get-wallet-stats"],"summary":"Get wallet trading stats","parameters":[{"schema":{"type":"string"},"description":"Ethereum wallet address","name":"wallet_address","in":"path","required":true}],"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"$ref":"#/components/schemas/internal_handler.WalletStats"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ft_market-service-v2_pkg_api.ErrorResponse"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ft_market-service-v2_pkg_api.ErrorResponse"}}}},"500":{"description":"Internal Server Error","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ft_market-service-v2_pkg_api.ErrorResponse"}}}}}}}},"components":{"schemas":{"internal_handler.WalletStats":{"type":"object","properties":{"avgTradeSize":{"type":"number"},"bestTrade":{"type":"number"},"buyVolume":{"type":"number"},"losingPredictions":{"type":"integer"},"losingSells":{"type":"integer"},"pnl":{"type":"number"},"predictionWinRate":{"type":"number"},"profitableSells":{"type":"integer"},"sellVolume":{"type":"number"},"sellWinRate":{"type":"number"},"totalVolume":{"type":"number"},"tradeCount":{"type":"integer"},"walletAddress":{"type":"string"},"winRate":{"type":"number"},"winningPredictions":{"type":"integer"},"worstTrade":{"type":"number"}}},"ft_market-service-v2_pkg_api.ErrorResponse":{"type":"object","properties":{"code":{"type":"integer"},"error":{"type":"string"},"message":{"type":"string"}}}}}}
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.42.space/for-developers/rest-api-alpha/leaderboard/get-wallet-trading-stats.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
