Honeycluster Docs – Fetch creator-distribution graphs for many tokens

tokens

Fetch creator-distribution graphs for many tokens

post

/token/flow/batch

operationId: token-flowBatch

POST batch variant of /token/{tokenSlug}/flow. Accepts { slugs: [...], maxDepth } (max 100 slugs, default depth 3). Each per-slug response is a BFS-rooted graph at the token issuer with cumulative drops volume on each edge — same shape as the single-slug endpoint.

Authorizations

Name	Location	Details
`BearerAuth`	Authorization header · bearer	JWT issued by the Honeycluster auth service for the `indexer` audience. Present as `Authorization: Bearer <token>`.

Request Body

application/json

required

Field	Type	Default	Description
`slugs` required	string[]		Array of token slugs in `currency.issuer` form (max 100 per request). Per-slug parse / lookup failures surface as `{ slug, data: null }` so a single bad slug doesn't take down the rest.
`maxDepth`	integer	`3`	Maximum BFS depth per token. Defaults to 3.

Example

Json

{
  "slugs": [
    "string"
  ],
  "maxDepth": 3
}

Responses

200

application/json

Successful response

Field	Type	Description
`items`	object[]	One entry per input slug, in the same order as the request. Always has the same length as `input.slugs`.
`items[].slug`	string	The token slug that produced this row (echoed from the request).
`items[].data`	object	Per-slug response, or `null` when the slug is malformed / unknown / the per-slug query threw.

Example

Json

{
  "items": [
    {
      "slug": "string",
      "data": {
        "nodes": [
          {
            "address": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
            "depth": 0,
            "totalReceived": "0",
            "currentBalance": "15000000000"
          },
          {
            "address": "rExampleEarly1234567890",
            "depth": 1,
            "totalReceived": "5000000000",
            "currentBalance": "4900000000"
          }
        ],
        "edges": [
          {
            "from": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
            "to": "rExampleEarly1234567890",
            "amount": "5000000000"
          }
        ]
      }
    }
  ]
}

400

application/json

Invalid input data

Field	Type	Description
`message`	string	The error message
`code`	string	The error code
`issues`	object[]	An array of issues that were responsible for the error
`issues[].message`	string

Example

Json

{
  "code": "BAD_REQUEST",
  "message": "Invalid input data",
  "issues": []
}

401

application/json

Authorization not provided

Field	Type	Description
`message`	string	The error message
`code`	string	The error code
`issues`	object[]	An array of issues that were responsible for the error
`issues[].message`	string

Example

Json

{
  "code": "UNAUTHORIZED",
  "message": "Authorization not provided",
  "issues": []
}

403

application/json

Insufficient access

Field	Type	Description
`message`	string	The error message
`code`	string	The error code
`issues`	object[]	An array of issues that were responsible for the error
`issues[].message`	string

Example

Json

{
  "code": "FORBIDDEN",
  "message": "Insufficient access",
  "issues": []
}

500

application/json

Internal server error

Field	Type	Description
`message`	string	The error message
`code`	string	The error code
`issues`	object[]	An array of issues that were responsible for the error
`issues[].message`	string

Example

Json

{
  "code": "INTERNAL_SERVER_ERROR",
  "message": "Internal server error",
  "issues": []
}