Skip to main content

Overview

This guide provides a step-by-step overview of integrating Bungee Auto into your application.

Integration Process Overview​

Integrating Bungee Auto involves 4 steps:

  1. Get a Quote: Fetch quote pricing information for the desired swap
  2. Create a Request: Prepare the swap request
  3. Request Submission: Submit the request either via the Submit API or Inbox Contract
  4. Monitor Status: Track the status of the swap

And that's it! Bungee Auto will handle the rest.

API Base URL​

The Bungee Auto API is available at:

https://public-backend.bungee.exchange

All API endpoints use this base URL. For details, see the API Reference.

This public endpoint is available for development and testing with a rate limit of 20 requests per minute (RPM). No authentication is required for the public endpoint.

Requesting Production API Access​

For production use with higher rate limits, please fill out the Bungee API Access Request Form to request dedicated API keys and access to our production endpoint.

Submission Methods​

Bungee Auto requests can be submitted in two ways:

1. API + Permit2 (for ERC20 tokens)​

This method uses the Bungee Auto API with Permit2 for gasless approvals:

  1. Get a quote from the Bungee API
  2. Create a request via the API
  3. Optionally: Approve Permit2 contract
  4. Sign a Permit2 message
  5. Submit the request with the signature
  6. Monitor the status via the API

This is the recommended approach for ERC20 tokens as it provides a better user experience by eliminating the need for separate approval transactions. Additionally, it allows for gasless approvals, saving users gas fees and tokens are only transferred if the auction is completed and a transmitter has picked up the request.

For a complete implementation guide, see Permit2 Integration (ERC20).

2. Inbox Contract​

This method uses the Bungee Auto inbox contract to directly submit the request onchain:

  1. Get a quote from the Bungee API
  2. Create and submit a request via the inbox contract
  3. Monitor the status via the API

This method is required for native tokens (ETH, MATIC, etc.) and can also be used for ERC20 tokens if Permit2 is not an option or if the integration is directly onchain.

For a complete implementation guide, see Inbox Contract Integration (Native).