> ## Documentation Index
> Fetch the complete documentation index at: https://developer.finogates.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get a Wallet's Activity by ID

> Get the money in-and-out history for a specific wallet by its UUID.

Unlike `GET /{user_id}/activity` — which only ever returns the user's
**primary** wallet's activity — this works for **any** wallet you own
(primary or not, user or master), so every wallet's history is reachable.
Use the `wallet_id` from `List All Wallets`, `List a User's Wallets`, or a
payment intent.

You get back the same shape as the by-user activity endpoint:

- **Balances** — `available`, `outbound_pending`, `inbound_pending`, and
  `current`.
- **Activity list** — one entry per payment, newest first, each with the
  journey, status, amount, direction (`amount_sign`), and timestamps.

The wallet must belong to your platform.



## OpenAPI

````yaml GET /v1/platform/wallets/by-id/{wallet_id}/activity
openapi: 3.1.0
info:
  title: Finogate Platform API v1
  version: 0.1.0
servers:
  - url: https://api-sandbox.finogates.com
    description: Sandbox
  - url: https://api.finogates.com
    description: Production
security: []
tags:
  - name: auth
  - name: users
  - name: payees
  - name: verification
  - name: bank accounts
  - name: card processing
  - name: digital-assets
  - name: international
  - name: onboarding
  - name: pending-applications
  - name: wallets
  - name: payments
  - name: catalog
  - name: webhooks
  - name: phone-numbers
  - name: sms
  - name: calls
  - name: listings
  - name: embed-tokens
paths:
  /v1/platform/wallets/by-id/{wallet_id}/activity:
    get:
      tags:
        - wallets
      summary: Get a Wallet's Activity by ID
      description: >-
        Get the money in-and-out history for a specific wallet by its UUID.


        Unlike `GET /{user_id}/activity` — which only ever returns the user's

        **primary** wallet's activity — this works for **any** wallet you own

        (primary or not, user or master), so every wallet's history is
        reachable.

        Use the `wallet_id` from `List All Wallets`, `List a User's Wallets`, or
        a

        payment intent.


        You get back the same shape as the by-user activity endpoint:


        - **Balances** — `available`, `outbound_pending`, `inbound_pending`, and
          `current`.
        - **Activity list** — one entry per payment, newest first, each with the
          journey, status, amount, direction (`amount_sign`), and timestamps.

        The wallet must belong to your platform.
      operationId: >-
        get_wallet_activity_by_id_v1_platform_wallets_by_id__wallet_id__activity_get
      parameters:
        - name: wallet_id
          in: path
          required: true
          schema:
            type: string
            format: uuid
            description: The wallet UUID.
            title: Wallet Id
          description: The wallet UUID.
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CommonResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - _AuthenticatedBearer: []
components:
  schemas:
    CommonResponse:
      properties:
        status_code:
          type: integer
          title: Status Code
          description: HTTP status code for the response.
        data:
          title: Data
          description: Payload or error details.
        query_generated_time:
          type: integer
          title: Query Generated Time
          description: >-
            UTC timestamp (milliseconds since epoch) when response was
            generated.
      type: object
      required:
        - status_code
        - data
        - query_generated_time
      title: CommonResponse
      description: |-
        Standard response wrapper for single-object responses and errors.

        Generic over the payload type. A route that declares
        ``CommonResponse[SomeModel]`` gets the real ``data`` schema rendered in
        OpenAPI/Swagger; a bare ``CommonResponse`` leaves ``data`` untyped.
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    _AuthenticatedBearer:
      type: oauth2
      flows:
        password:
          scopes: {}
          tokenUrl: /v1/platform/auth/token

````