Skip to main content

Integrator Guidelines

Jupiter provides developer tools and resources to help you integrate with Jupiter. The following section provides the guidelines when integrating with Jupiter.

Branding and Marketing

When integrating with Jupiter, you can use the following assets to help you brand and market your product: Jupiter Brand Assets.

Labelling Routing Provider

Do note that, if you are using our routing engine (such as getting quotes from the Swap API), you are to label the routing provider as "Jupiter Metis v1", and not "Jupiter".

Developer Support

There are currently 2 ways to get technical support:

  1. Public Developer Support Channel in Discord
  2. Portal Enquiry
warning

Please use the Discord channel for your technical questions, as it is a public channel, more people can help you and it promotes discovery/discussion.

If you open a ticket via the link that does not relate to Portal Enquiries, we will redirect you to the Discord channel.

Customer Support

The Jupiter UI contains multiple safeguards, warnings and default settings to guide our users to trade safer. However, when you integrate with Jupiter, we cannot control these elements despite sharing best practices, hence, Jupiter is not liable for any losses incurred on your UI/platform.

The only exception is for Jupiter Ultra API, where you can use our ticketing system to provide support to your users.

warning

We are still in the process of finalizing the Ultra API customer support process.

Reach out to us to discuss what is the best way to support your users.