LI.FI — Get the total amount of a token received on a specific chain, for cross-chain transfers.

Calculates and returns the total received token amount per wallet address, per sending chain, within a specified time range, for a given receiving chain and receiving token. The request takes a from timestamp, a to timestamp and a to chain. Request fields include result limit (limit). Use it in blockchain research or an on-chain monitoring dashboard. The GET request schema also lists fromTimestamp, toTimestamp, toChain. Use the response in a DeFi workflow for the selected protocol, and compare the request and response with the provider example.

Selected price
$0 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
A Unix timestamp in seconds marking the start of the query period, inclusive. Transactions older than this timestamp will not be included in the summary.
A Unix timestamp in seconds marking the end of the query period, inclusive. Transactions after this timestamp will not be included in the summary. **The maximum range supported by the endpoint is 30 days.**
The ID, or key of the chain on the receiving side of the transfer. This parameter filters the summary to include only transfers received on the specified chain.
The address, or symbol of the token received in the transfers. This parameter filters the summary to include only transfers involving the specified token on the receiving chain.
Optional parameters (5)
Pagination limit. Defines the maximum number of returned results.
The next page cursor. Must come from the `next` field of the response of the previous request.
The previous page cursor. Must come from the `previous` field of the response of the previous request.
The ID, or key of the chain on the sending side of the transfers. This parameter filters the summary to include only transfers sent from the specified chain.
The integrator string to filter transfers by. This parameter filters the summary to include only transfers for the given integrator.

Sample response

{
  "data": [
    {
      "id": {
        "sendingChainId": 1,
        "toAddress": "0x21498e23c1eb1a097be1ed1321c6de1819e49621"
      },
      "totalReceivedAmount": 618132975599
    }
  ],
  "hasNext": true,
  "hasPrevious": false,
  "next": "WzYxODEzMjk3NTU5OSx7InRvQWRkcmVzcyI6IjB4MjE0OThlMjNjMWViMWEwOTdiZTFlZDEzMjFjNmRlMTgxOWU0OTYyMSIsInNlbmRpbmdDaGFpbklkIjoxfV0",
  "total": 0
}

Response result

Response structure

Inferred from examples
  • dataobject[]
    • idobject
      • sendingChainIdinteger
      • toAddressstring
    • totalReceivedAmountinteger
  • hasNextboolean
  • hasPreviousboolean
  • nextstring
  • totalinteger

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use LI.FI — Get the total amount of a token received on a specific chain, for cross-chain transfers. with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.