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

# Wallet transactions

> Wallet transactions.



## OpenAPI

````yaml GET /account/wallet/transactions
openapi: 3.0.3
info:
  title: OnlyTraffic Studio API
  version: 1.0.0
  description: >-
    External API for OnlyTraffic Studio. Manage and retrieve data about your
    subscribers, CPL orders, and CPC orders.
servers:
  - url: https://studio-api.onlytraffic.com/api/external/v1
security:
  - ApiKeyAuth: []
tags:
  - name: Account
    description: API key holder's wallet, profile, and aggregate state.
  - name: Accounts
    description: OnlyFans accounts attached to the API key holder.
  - name: Agencies
    description: Agency CRUD and image management. All edits stage in moderation.
  - name: CPL
    description: >-
      Cost-per-lead orders: place, list, cancel, manage settings, browse partner
      offers.
  - name: CPC
    description: Cost-per-click orders and creative management.
  - name: RevShare
    description: Revenue-share campaigns and invoices.
  - name: Swaps
    description: Two-sided traffic swap orders and offers.
  - name: Subscribers
    description: Per-fan delivery feed (cursor-paginated).
  - name: Transactions
    description: Per-transaction OF revenue feed (cursor-paginated).
paths:
  /account/wallet/transactions:
    get:
      tags:
        - Account
      summary: Wallet transactions
      description: Wallet transactions.
      operationId: getAccountWalletTransactions
      parameters:
        - name: after
          in: query
          schema:
            type: string
          description: >-
            Cursor from a previous response's `pagination.next_cursor`. Omit for
            the first page.
        - name: limit
          in: query
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 50
          description: Page size. Default 50, max 100.
        - name: sort
          in: query
          schema:
            type: string
            enum:
              - date_desc
              - date_asc
            default: date_desc
          description: >-
            Sort order. The cursor is bound to the direction it was issued for;
            switching mid-pagination requires restart.
        - name: transaction_id
          in: query
          schema:
            type: string
            format: uuid
          description: >-
            Exact-match lookup by `transaction_id` (the `transaction_uuid` from
            the response).
        - $ref: '#/components/parameters/FromDate'
        - $ref: '#/components/parameters/ToDate'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: true
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/WalletTransaction'
                  pagination:
                    $ref: '#/components/schemas/CursorPagination'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '429':
          description: Rate limit exceeded
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: >-
            Server error. Body always reads `{success:false,
            error:"server_error", message:"Server error"}` (no internal details
            leak).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  parameters:
    FromDate:
      name: from
      in: query
      schema:
        type: string
        format: date
      description: Lower bound on the resource date (`YYYY-MM-DD`, UTC, inclusive).
      example: '2026-01-01'
    ToDate:
      name: to
      in: query
      schema:
        type: string
        format: date
      description: Upper bound on the resource date (`YYYY-MM-DD`, UTC, inclusive).
      example: '2026-01-31'
  schemas:
    WalletTransaction:
      type: object
      description: >-
        Single entry in the wallet ledger. Positive `amount` = credit, negative
        = debit.
      properties:
        transaction_id:
          type: string
          format: uuid
          description: Stable, unique ledger entry id.
          example: 6c0a2cf7-0c91-4f7a-8a45-7eaf9d51b211
        action:
          type: string
          enum:
            - top_up
            - cover_deposit
            - refund_deposit
            - invoice
            - reserve
            - reserve_revert
            - campaign_preorder
            - campaign_preorder_revert
            - campaign_complete
            - campaign_chunk
            - campaign_hold_release
            - payout
            - ppc
            - ppc_complete
            - ppc_revert
            - swap
            - swap_revert
            - swap_price
            - swap_fans
            - swap_complete
            - revshare
            - referrals
            - manager_payment
            - manager
            - refund
            - unknown
          description: >-
            What this entry does to the balance. `unknown` covers transaction
            types not yet documented; check the web dashboard for details.
          example: reserve
        amount:
          type: number
          format: float
          description: Signed change applied to the wallet balance.
          example: -100
        balance_after:
          type: number
          format: float
          description: >-
            Wallet balance immediately after this entry. Use it to reconcile
            against your own books without recomputing.
          example: 1184.5
        description:
          type: string
          nullable: true
          description: >-
            Plain-text human description. For `unknown` actions, returns a
            generic placeholder pointing to the web dashboard.
          example: Reserve for CPL order cplo_xxxxxxx
        date:
          type: string
          format: date-time
          example: '2026-01-15T12:00:00+00:00'
        date_ts:
          type: integer
          example: 1736942400
    CursorPagination:
      type: object
      description: >-
        Cursor-based pagination (used by high-volume feeds: `subscribers`,
        `transactions`).
      properties:
        next_cursor:
          type: string
          nullable: true
          description: >-
            Opaque token. Pass it as `?after=...` to get the next page. `null`
            when there are no more rows.
          example: eyJ0cyI6MTc0NjQ1MzI5NiwiaWQiOjk4NzY1fQ==
        has_next:
          type: boolean
          description: '`true` if more rows remain after this page.'
          example: true
        limit:
          type: integer
          description: How many rows were requested for this page.
          example: 50
    ErrorResponse:
      type: object
      description: Standard error envelope for all 4xx/5xx responses.
      required:
        - success
        - error
        - message
      properties:
        success:
          type: boolean
          enum:
            - false
          description: Always false on error responses.
        error:
          type: string
          description: Stable snake_case machine-readable error code. Branch on this.
          example: validation_failed
        message:
          type: string
          description: >-
            Human-friendly text. For 5xx this is always the literal `Server
            error`. For 4xx an actionable validation/auth message is returned.
        details:
          type: object
          nullable: true
          description: >-
            Optional per-field diagnostic information. On 422 carries `{<field>:
            ["error_code", ...]}`. On 402 (`insufficient_balance`) carries
            `{required, current}`. On 426 (`unpaid_invoices`) carries `{count,
            total, oldest_date_ts}`. Absent on most other errors.
          additionalProperties: true
        retry_after:
          type: integer
          nullable: true
          description: >-
            Seconds until the next request will succeed. Present only on 429
            responses (rate limit). Mirrors the `Retry-After` HTTP header.
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key
      description: Your API key from the Studio Dashboard

````