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

# Direct user-to-user transfer edges among a wallet set

> Returns the set of direct transfer edges (user-to-user, scoped to
a mint) where both endpoints are in the supplied wallet list.
Edges are canonical (`a < b` lex), undirected, and aggregated —
repeated transfers between the same pair collapse to one row with
a `transfers` count.

Used by the bubblemap to draw lines between holders that have
directly interacted; useful generally for "did wallet A ever send
tokens to wallet B?" style queries.




## OpenAPI

````yaml openapi-spec/history.yaml get /api/sol/holder-edges
openapi: 3.0.3
info:
  title: Raze Database API
  description: >
    Paid subscription API for Solana transaction data and history.


    Also hosts write utilities (`/utils/sol/*`): token launch, transfer, burn,

    consolidate, fees claim/config, and agent initialize — previously on

    `router.raze.bot`. Mixer/distribute removed 2026-07-25.


    ## Batch Requests

    All endpoints with path parameters (mint, signer, address, tokenMint,
    ownerAddress) support batch queries

    via comma-separated values. For example:
    `/api/sol/trades/mint/mint1,mint2,mint3?limit=50`


    - Maximum 10 values per batch request

    - Each value must be a valid address (>= 32 characters)

    - Single values behave identically to non-batch requests

    - Batch response format: `{ "success": true, "results": { "value1": {...},
    "value2": {...} }, "count": N, "timestamp": "..." }`

    - Each key in `results` contains the full single-entity response

    - Queries run in parallel for maximum performance
  version: 1.0.0
servers:
  - url: https://api.raze.bot
    description: >-
      Raze global History API — GeoDNS routes to the nearest region
      automatically
security:
  - ApiKeyAuth: []
paths:
  /api/sol/holder-edges:
    get:
      summary: Direct user-to-user transfer edges among a wallet set
      description: |
        Returns the set of direct transfer edges (user-to-user, scoped to
        a mint) where both endpoints are in the supplied wallet list.
        Edges are canonical (`a < b` lex), undirected, and aggregated —
        repeated transfers between the same pair collapse to one row with
        a `transfers` count.

        Used by the bubblemap to draw lines between holders that have
        directly interacted; useful generally for "did wallet A ever send
        tokens to wallet B?" style queries.
      operationId: holderEdges
      parameters:
        - name: mint
          in: query
          required: true
          schema:
            type: string
          example: So11111111111111111111111111111111111111112
        - name: wallets
          in: query
          required: true
          schema:
            type: string
          description: One or more wallet addresses (comma-separated, max 150).
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HolderEdgesResponse'
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    HolderEdgesResponse:
      type: object
      properties:
        success:
          type: boolean
        mint:
          type: string
        edges:
          type: array
          items:
            $ref: '#/components/schemas/HolderEdge'
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
        message:
          type: string
        code:
          type: string
        success:
          type: boolean
      example:
        error: Unauthorized
        message: Invalid API key
        code: INVALID_KEY
        success: false
    HolderEdge:
      type: object
      properties:
        a:
          type: string
          description: >-
            Lexicographically lower of the two wallet addresses (canonical
            ordering).
        b:
          type: string
          description: Lexicographically higher of the two wallet addresses.
        kind:
          type: string
          enum:
            - token
            - sol
          description: |
            - `token` — SPL transfer of the mint
            - `sol`   — native SOL transfer between the same two wallets
        transfers:
          type: integer
          description: Number of transfers between this pair (aggregated).
        firstSeen:
          type: string
          format: date-time
        lastSeen:
          type: string
          format: date-time
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: query
      name: apiKey

````