Overview
This node integrates with the Jupiter Price API v3 to fetch price information for specified tokens. It is useful in scenarios where you need up-to-date token prices on the Solana blockchain or other supported tokens, such as for portfolio valuation, trading bots, or analytics dashboards.
For example, you can input a list of token mint addresses and get their current prices quoted against a specific token like USDC. Optionally, you can request additional token metadata to enrich your data.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base URL endpoint for the Jupiter Price API v3 (default: https://lite-api.jup.ag/price/v3) |
| Token IDs | Comma-separated list of token mint addresses to retrieve prices for (required) |
| VS Token | The symbol of the token to price against (default: USDC) |
| VS Token Address | Optional token address to price against instead of symbol |
| Show Extra Info | Boolean flag to include additional token information in the response |
Output
The node outputs an array with one item per input. Each item's json field contains the JSON response from the Jupiter Price API v3 /price endpoint. This includes price data for the requested tokens, optionally enriched with extra token info if enabled.
If an error occurs for an item, the output JSON will contain an error field with the error message.
No binary data is produced by this node.
Dependencies
- External HTTP access to the Jupiter Price API v3.
- Optionally, an API key credential can be provided to authenticate requests via the
x-api-keyheader. This is not mandatory but may be required depending on API usage limits or access policies.
Troubleshooting
- Missing or invalid Token IDs: The node requires at least one valid token mint address. Ensure the
Token IDsproperty is correctly set as a comma-separated string. - API errors or rate limits: If the API returns errors, check if an API key is needed and configured properly.
- Network issues: Verify that the n8n instance has internet access to reach the Jupiter API endpoint.
- Invalid VS Token or VS Token Address: Providing both or incorrect values might cause unexpected results; use either the symbol or the address appropriately.
Common error messages:
"Request failed"or similar HTTP errors indicate connectivity or API issues."Invalid token ID"suggests malformed or unsupported token mint addresses.
Links and References
- Jupiter Aggregator API Documentation (for detailed API usage and parameters)
- Solana Token List (to find valid token mint addresses)