Tanner Moore I Secure 1inch API Integration Using Vercel Proxy I ETHGlobal Taipei 2025

[Music] One unique quality of the 1-in API is it does not accept requests from an internet browser. This is because any website that integrates 1 in like this would be exposing the API key for malicious users to take and use independently. To get around this, a proxy must be used for all requests. Luckily, with a tool like Verscell, setting up a proxy only takes a couple minutes. Let's take a look at how to do that.

Now, this is a GitHub repo linked in our documentation that can quickly be deployed to the cloud hosting service for cell. It will provide a cloud endpoint for all of your 1-in API requests. Once this proxy receives the API requests, it will attach the authorization header for you and send the request to the 1-in API. The response will come back just as if there was no proxy at all. So, let's quickly set this up.

The first thing mentioned in the readme is the Verscell account. I already have mine, so I'm not going to make a new account, but that's pretty self-explanatory. Just make sure to choose the hobby tier because this whole process will be free. Once you have your free account, you're going to create your project. And here you're going to click import third-party git repository.

You will go back to this GitHub repo, paste it in here, and click continue. It will be on this section of the UI once it's imported. And then you can click import to add it to your project. I'm going to leave these all defaults. Add test and deploy.

says congratulations and we can continue to dashboard. Now we're going to click on settings environment variables and here we're going to put API off token and paste in our developer portal key. Click save and we can see it added right here. At the bottom you'll see a notification that we need to deploy again but we will do that at the end once all the setup is complete. And the last thing we need to do is go to deployment protection and disable Verscell authentication.

Save. And now we can redeploy. And now if we go back to our project tab, we will see under domains our new URL that will handle all requests to the 1-in API. And now to prove it's all working, we have a simple gas price call, but instead of going to api1in.dev, we replace that with our versel proxy address.

Hit enter and we get the JSON response body for gas information. So this now shows the proxy API endpoint handling the requests adding on the authorization header and returning the response just as if you were talking to the 1-in API directly. [Music]