POST

/v1/transactions

Transactions between two addresses. Direct edges on EVM chains, shared-transaction traversal on BTC.

Answers the direct question "did A ever pay B". On EVM chains this reads the direct edges between the two addresses, native and token. On Bitcoin the model is different: the graph is bipartite through transactions rather than address to address, so the traversal goes through shared transactions and an economic hop there is two hops in the graph.

Request

curl -X POST https://intelapi.publicaml.org/v1/transactions \
  -H 'Content-Type: application/json' \
  -d '{
  "from": "0x…",
  "to": "0x…",
  "chain": "BSC",
  "limit": 50
}'

Response

{
  "from": "0x08723392ed15743cc38513c4925f5e6be5c17243",
  "to": "0xdac17f958d2ee523a2206206994597c13d831ec7",
  "chain": "ETH",
  "count": 0,
  "limit": 5,
  "offset": 0,
  "transactions": []
}

Response fields

Field	Type	Meaning
count	number	Rows returned in this page.
transactions[]	array	Transaction hash, block number, timestamp, token, amount and direction.
offset	number	Paging offset echoed back.

Things that catch people out

An empty transactions[] with count 0 is a real "no link found", not an error. The HTTP status is 200.
Bitcoin hops are not comparable to EVM hops. See the note in the fund-flow docs before comparing distances across chains.

Try it

The interactive console runs this endpoint against live data from the browser, with no key and no signup.

Open the sandbox at intelapi.publicaml.org