> ## Documentation Index > Fetch the complete documentation index at: https://docs.testnet.dev.adipredictstreet.com/llms.txt > Use this file to discover all available pages before exploring further. # Public activity for the user (trades + position split/merge) > Cursor-paginated feed of `trades` plus CTF position events (`Vault.splitPosition` / `Vault.mergePositions`, surfaced as `kind=position_split|position_merge`). Settlements and on-chain transfers are tied to the wallet's funds and remain private to `/api/me/activity`. Optional `type` narrows the feed with the same vocabulary as `/api/me/activity` (coarse groups + fine-grained `buys|sells|splits|merges|...`), intersected with the public category set: a private slice (`settlements`, `transfers`, `deposits`, `withdrawals`) validates but returns an empty page, and the `counts` block always reports those private buckets as 0 (`counts.all` = trades + positions) — only trade/position badges are public. NOTE: the default page (no `type`) reports `type:"trades"` for legacy client routing but INCLUDES split/merge rows; an explicit `?type=trades` is trades-only (splits/merges live under `?type=positions`). Filtering applies before pagination. `limit` clamped to 1..100, default 20. ## OpenAPI ````yaml /api-reference/openapi.json get /api/users/{address}/activity openapi: 3.1.0 info: title: PredictStreet API description: >- Client-facing HTTP API for the PredictStreet prediction-market platform. **Partner kinds.** Every authenticated endpoint resolves a request's *effective wallet* from the partner row. `single_wallet` partners bind to one `associatedWallet` set at creation. `multi_wallet` partners declare the actor on every request via an `X-User-Wallet: 0x<40-hex>` header. See the [Partner kinds](/auth/api-keys#partner-kinds) doc for the full contract. version: '2026-06-16' contact: name: PredictStreet partners email: partners@predictstreet.com servers: - url: https://core.api.dev.predictstreet.sde.adifoundation.ai description: Testnet (partner integrator API — final domain TBD) security: [] tags: - name: Deposits description: >- Gasless USDC deposit relay - submit a signed EIP-2612 permit and the platform broadcasts the on-chain deposit for you (no gas). - name: Events description: >- Polymarket-style event grouping with football metadata (group, stage, teams, tags). - name: Tags description: Curated tag taxonomy used to filter events. - name: Markets description: 'Public market data: list, detail, orderbook, trades, OHLC.' - name: Crypto description: >- Crypto price markets: the underlying-asset price curve and Up/Down series navigation. The markets themselves are ordinary binary markets — list them through /api/markets and /api/events. - name: Orders description: >- Signed-order place / cancel / read. Requires `X-Api-Key` with `orders:read` / `orders:write` scope; every write additionally requires an EIP-712 signature over the order. - name: Portfolio description: >- Balances, positions, trades, fees, vault info for the key's `associatedWallet`. Requires `X-Api-Key` with `portfolio:read` scope. - name: Matches description: >- A match groups several events into one fixture/card (1X2 + first-scorer + over-under under one matchup). - name: Vault description: >- Backend co-signatures for ERC-1155 split / merge, and recovery for off-chain locks when the corresponding chain tx never confirmed. Requires `X-Api-Key` with `vault:write` scope plus an EIP-712 signature over the operation. - name: Leaderboard description: Public ranked leaderboard across PnL / volume buckets. - name: Search description: Global search across users, events, and matches. - name: Withdrawal Security description: >- Self-service withdrawal 2FA (TOTP) and withdrawal-address whitelist. Same endpoints serve the web app (user sessions) and API-key integrators. Mutations need `vault:write`, reads `portfolio:read`. Both are opt-in per wallet and only gate withdrawals once the platform enables withdrawal-security enforcement. - name: Platform description: >- Public platform state: the contract registry, the platform fee configuration, the platform freeze flag and active notices. No authentication. paths: /api/users/{address}/activity: get: tags: - Public Profile summary: Public activity for the user (trades + position split/merge) description: >- Cursor-paginated feed of `trades` plus CTF position events (`Vault.splitPosition` / `Vault.mergePositions`, surfaced as `kind=position_split|position_merge`). Settlements and on-chain transfers are tied to the wallet's funds and remain private to `/api/me/activity`. Optional `type` narrows the feed with the same vocabulary as `/api/me/activity` (coarse groups + fine-grained `buys|sells|splits|merges|...`), intersected with the public category set: a private slice (`settlements`, `transfers`, `deposits`, `withdrawals`) validates but returns an empty page, and the `counts` block always reports those private buckets as 0 (`counts.all` = trades + positions) — only trade/position badges are public. NOTE: the default page (no `type`) reports `type:"trades"` for legacy client routing but INCLUDES split/merge rows; an explicit `?type=trades` is trades-only (splits/merges live under `?type=positions`). Filtering applies before pagination. `limit` clamped to 1..100, default 20. operationId: PublicProfileController_activity parameters: - name: address required: true in: path schema: type: string - name: cursor required: false in: query schema: type: string - name: limit required: false in: query schema: type: integer minimum: 1 maximum: 100 default: 20 - name: type required: false in: query schema: enum: - all - trades - settlements - transfers - positions - buys - sells - splits - merges - deposits - withdrawals type: string responses: '200': description: '' content: application/json: schema: $ref: '#/components/schemas/PublicActivityDto' components: schemas: PublicActivityDto: type: object properties: items: type: array items: type: object additionalProperties: true description: >- Trade rows + CTF position events (`Vault.splitPosition` / `Vault.mergePositions`). Settlements and on-chain transfers are omitted — they remain private to `/api/me/activity`. nextCursor: type: string nullable: true hasMore: type: boolean required: - items - nextCursor - hasMore ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.