Skip to main content
POST
/
v0
/
relationships
/
subgraph
Get Subgraph Relationships
curl --request POST \
  --url https://api.bubblemaps.io/v0/relationships/subgraph \
  --header 'Content-Type: application/json' \
  --header 'X-ApiKey: <api-key>' \
  --data '
{
  "addresses": [
    "<string>"
  ],
  "context_token_key": {
    "chain": "eth",
    "address": "<string>"
  }
}
'
[
  {
    "from_address": "<string>",
    "to_address": "<string>",
    "data": {
      "total_value": 123,
      "total_transfers": 123,
      "first_date": 123,
      "last_date": 123,
      "token_key": {
        "chain": "eth",
        "address": "<string>"
      }
    },
    "rel_type": "GROUPED_TRANSFER"
  }
]

Documentation Index

Fetch the complete documentation index at: https://docs.bubblemaps.io/llms.txt

Use this file to discover all available pages before exploring further.

Credit cost: 10 per request + 1 per requested address.
Get all the transfers between a given list of addresses. By default, only the transfers of indexed tokens are included. Use the context_token_key body parameter to force the inclusion of transfers of a specific token.
Transfers are grouped based on the (from_address, to_address, token_ref) key. Meaning that if A sends some BMT to B multiple times, these transfers will be grouped as a unique GROUPED_TRANSFER relationship object.
Other types of relationships with different data schemas will be supported in the future, make sure this doesn’t break your typing.
Relationships between two supernodes (addresses with high volume of transfers) are ignored. Rrelationships between a supernode and a non-supernode are included though.

Authorizations

X-ApiKey
string
header
required

Body

application/json
addresses
string[]
required
Required array length: 2 - 1000 elements
context_token_key
TokenKey · object

Response

Successful Response

from_address
string
required
to_address
string
required
data
GroupedTransferDataV0 · object
required
rel_type
string
default:GROUPED_TRANSFER
Allowed value: "GROUPED_TRANSFER"