Invia Docs

REST API/Tokens & trending

These endpoints proxy public Jupiter data. The Invia backend caches and rate-limits them so SDK consumers do not have to manage their own Jupiter rate limits.

`GET /v1/tokens`

Resolve metadata for a list of mints in one round trip.

Query parameters

Name	Type	Notes
`mints`	`string`	Comma-separated list of base58 mints. Required.

Response

{
  "tokens": [
    {
      "mint": "Es9...",
      "symbol": "BONK",
      "name": "Bonk",
      "decimals": 5,
      "imageUrl": "https://..."
    }
  ]
}

Any mint that Jupiter does not recognize comes back with null symbol/name and a numeric decimals read from the chain.

`GET /v1/trending`

Cached snapshot of Jupiter's top organic mints, useful for surfacing candidates in a swap interface.

Response

{
  "items": [
    {
      "mint": "Es9...",
      "symbol": "BONK",
      "name": "Bonk",
      "imageUrl": "https://...",
      "priceUsd": 0.000018,
      "change24h": 4.2,
      "volume24h": 12000000,
      "liquidityUsd": 4500000,
      "fdv": 1500000000,
      "marketCap": 1200000000,
      "holders": 730000,
      "organicScore": 87.5,
      "isVerified": true,
      "dexscreenerUrl": "https://dexscreener.com/solana/..."
    }
  ],
  "fetchedAt": 1745678400,
  "source": "cache",
  "count": 50
}

fetchedAt is a unix-seconds timestamp; source indicates whether the response was served from the in-memory cache or just refreshed.