Jupiter Ultra icon

Jupiter Ultra

Jupiter Ultra API operations
Join our community

Actions6

Overview

This node integrates with the Jupiter Ultra API, providing various operations related to token swaps and liquidity on Solana. The Shield operation specifically fetches token risk warnings for a list of mint addresses. This is useful for users who want to assess the risk profile or safety concerns associated with specific tokens before interacting with them.

Practical scenarios include:

  • Checking if certain tokens have any known risks or warnings before trading or holding them.
  • Filtering tokens based on their risk status in automated workflows.
  • Enhancing security by integrating risk information into token management processes.

Properties

Name Meaning
Base URL The base URL for the Jupiter Ultra API. Defaults to https://lite-api.jup.ag/ultra/v1.
Mints Comma-separated list of mint addresses to check for risk warnings (optional).

Output

The output JSON contains the response from the Jupiter Ultra API's /shield endpoint. It provides token risk warning information corresponding to the requested mint addresses. The exact structure depends on the API but typically includes details about each token's risk status or warnings.

No binary data is output by this operation.

Example output snippet (conceptual):

{
  "tokens": [
    {
      "mint": "mint_address_1",
      "riskWarnings": ["warning1", "warning2"]
    },
    {
      "mint": "mint_address_2",
      "riskWarnings": []
    }
  ]
}

Dependencies

  • Requires access to the Jupiter Ultra API, optionally using an API key credential if provided.
  • No mandatory credentials are required, but if an API key credential is configured, it will be sent as an x-api-key header.
  • Network connectivity to the specified Base URL.

Troubleshooting

  • Common issues:

    • Invalid or malformed mint addresses may cause the API to return errors or empty results.
    • Network or connectivity problems can lead to request failures.
    • If using an API key, ensure it is valid and has sufficient permissions.

  • Error messages:

    • "Unknown operation: shield" — indicates the operation parameter was not set correctly; ensure "Shield" is selected.
    • HTTP errors from the API (e.g., 400 or 500) usually indicate invalid parameters or server issues; verify inputs and try again.
    • If the node throws errors about missing credentials, either provide a valid API key credential or leave it blank if not required.

Links and References

Discussion