Sushi API gives 502 errors all time

[luiztools]

I've tried to use the Sushi API to get swap, but it gives me 502 erro all time: https://docs.sushi.com/api/swagger

I've tried to use the Sushi SDK to get swap, but it gives me the same error (code below): https://docs.sushi.com/sdk/swap

async function start(){
    const data = await getSwap({
        chainId: ChainId.SEPOLIA, 
        tokenIn: process.env.TOKEN0_ADDRESS, // eth token
        tokenOut: '0x6B3595068778DD592e39A122f4f5a5cF09C90fE2', // sushi token
        sender: process.env.WALLET,
        amount: ethers.parseEther(process.env.AMOUNT_TO_BUY),
        maxSlippage: 0.005, // 0.05% max slippage
    });
    console.log(data);
}

start();

So I've tried to interact directly with the Red Snwapper, but I don't know what to pass in the executor (maybe the Router Processor address?) and executorData: https://docs.sushi.com/contracts/red-snwapper

Anyone could help me to integrate my swap software to SushiSwap?

[banlieu451]

There si no support into this shit protocol leave this it is better for everyone

[luiztools]

Hey, apologies, we don't really check the org discussions 😅

As for your code - Sepolia is currently not supported by the Swap API I'm afraid, that's why you're seeing an error. 502 is definitely not the right one for this though, we should definitely use a 4xx range code with ideally a status msg.

Do you have any list or docs with the supported networks? Specially if there is any testnet to do some tests.

[LufyCZ]

Hey, apologies, we don't really check the org discussions 😅
As for your code - Sepolia is currently not supported by the Swap API I'm afraid, that's why you're seeing an error. 502 is definitely not the right one for this though, we should definitely use a 4xx range code with ideally a status msg.

Do you have any list or docs with the supported networks? Specially if there is any testnet to do some tests.

All evm chains listed in our frontend should be supported. For testnets, there's Tatara (129399), but no promises on how long that'll stay up.

[luiztools]

Hey, apologies, we don't really check the org discussions 😅
As for your code - Sepolia is currently not supported by the Swap API I'm afraid, that's why you're seeing an error. 502 is definitely not the right one for this though, we should definitely use a 4xx range code with ideally a status msg.

Do you have any list or docs with the supported networks? Specially if there is any testnet to do some tests.

All evm chains listed in our frontend should be supported. For testnets, there's Tatara (129399), but no promises on how long that'll stay up.

I've tried Tatara Testnet with getSwap from Sushi SDK, but I receive an "Failed to fetch swap: Internal Server Error"

So I've tried to interact directly with the Red Snwapper, but I don't know what to pass in the executor (maybe the Router Processor address?) and what is executorData? https://docs.sushi.com/contracts/red-snwapper

[LufyCZ]

Tatara supports was removed I think yesterday, terrible timing 😅

@matthewlilley maybe we should consider choosing one testnet and keeping it alive.

There's now a /chain-ids endpoint btw

[matthewlilley]

Hey, apologies, we don't really check the org discussions 😅
As for your code - Sepolia is currently not supported by the Swap API I'm afraid, that's why you're seeing an error. 502 is definitely not the right one for this though, we should definitely use a 4xx range code with ideally a status msg.

Do you have any list or docs with the supported networks? Specially if there is any testnet to do some tests.

All evm chains listed in our frontend should be supported. For testnets, there's Tatara (129399), but no promises on how long that'll stay up.

I've tried Tatara Testnet with getSwap from Sushi SDK, but I receive an "Failed to fetch swap: Internal Server Error"

So I've tried to interact directly with the Red Snwapper, but I don't know what to pass in the executor (maybe the Router Processor address?) and what is executorData? https://docs.sushi.com/contracts/red-snwapper

Maybe you can help us understand your need for a testnet? We support over 40 chains, and some that are practically free to use.

Also, if you're having issues with getSwap please share a reproducable example or it is difficult for us to assist you.

[luiztools]

@matthewlilley We need at least one testnet for...tests, right? Why I'll do real swaps with real coins to just test a proof of concept code? I'm not afraid of gas fees, but the coins itself.

I sent the code that I'm using in the first message. I'm using the Sushi SDK. Do you need the entire project folder with package.json and etc? I can upload and send if necessary.

And about the Red Snwapper, my second option, I didn't understand what pass in the executor and executorData params, the function is very different than Uniswap and PancakeSwap, the dexes that I'm more experienced to integrate with via smart contracts.

[matthewlilley]

Understood, I'll look at enabling Sepolia and keeping that up permanently but can't promise it will be useful for your use case. IMHO it would be better for you to test with simulations, not actual calls, on a real network. There is no cost or risk involved and you will get real world data and results from it.

Your code looks fine, though I cannot see what you're using for source, it should be sender (EOA) or self (Contract).

You cannot use RedSnwapper without getting prepared data from our API, it is a facade that simply passes execution data through to our executors, it's not meant to be used without data we've prepared and supplied through our API. It's unique to us, Pancake nor Uniswap have sophisticated aggregation capabilities, closest would be 1inch.

[luiztools]

I teach web3 programming in my Youtube channel, weblog, books and courses so I need to be more as more didatic as possible. I have lessons with Uniswap and PancakeSwap and thought that would be interesting to have lessons with Sushi too. Basically I want to teach how to integrate Node.js backends and console apps with Sushi to do swaps based on market observation triggers (I already have the market observation part done, with subgraphs). So, the sender of the calls is a wallet (EOA), as MetaMask.

I'm not sure if the API will help me, because with Pancake and Uni, I've a router contract that I just call a function sending the right parameters and the swap is done (including at testnet), but with Sushi I've tried different things looking in the docs without success. I can't even find a router contract at v3 docs, just v2, and the routers that I've found looks to be connected to the RedSnwapper that you mentioned that won't work for me.

[matthewlilley]

I teach web3 programming in my Youtube channel, weblog, books and courses so I need to be more as more didatic as possible. I have lessons with Uniswap and PancakeSwap and thought that would be interesting to have lessons with Sushi too. Basically I want to teach how to integrate Node.js backends and console apps with Sushi to do swaps based on market observation triggers (I already have the market observation part done, with subgraphs). So, the sender of the calls is a wallet (EOA), as MetaMask.

I'm not sure if the API will help me, because with Pancake and Uni, I've a router contract that I just call a function sending the right parameters and the swap is done (including at testnet), but with Sushi I've tried different things looking in the docs without success. I can't even find a router contract at v3 docs, just v2, and the routers that I've found looks to be connected to the RedSnwapper that you mentioned that won't work for me.

Gotcha. That's great to hear and feel free to drop the link here so I and others can take a look.

I'll get Sepolia spun up for you, this is probably the best one to use because it likely has many other real protocols which we use as apart of our aggregation.

The SDK uses the API, the API can be used independently as well. Both methods are documented in our docs:

https://docs.sushi.com/api/examples/swap

https://docs.sushi.com/sdk/swap

Uniswap & Pancake both have naive routing & routers. Sushi uses a route processor which processes complex routes computed off chain for maximum benefit of users, far superior to other dex routers.

There is also examples of using a contract to call RedSnwapper if that's something that you have in mind as well:

https://docs.sushi.com/contracts/red-snwapper#using-a-contract-to-call-redsnwapper

I'll get back to you once we have spun up sepolia.

[matthewlilley]

@luiztools sepolia is live on production API, let me know if you have any issues

[luiztools]

It worked like a charm, thanks!