Simple Discord Webhook Proxy - Easily host your own Free Webhook Proxy in 1-click! [Open-Source]

Resources Community Resources
, , ,
#1

:globe_with_meridians: Easily host your own Discord Webhook Proxy

Hello all,

I recently saw that @lewisakura’s public proxy was experiencing load/request handling issues so I made a simple version that can easily be deployed in one-click!

This Simple Discord Webhook Proxy is the perfect solution for Roblox developers and anyone working with Discord webhooks. Seamlessly send webhooks through Vercel’s global network with just a minor URL tweak.

:zap: Key Features:

  • :bulb: Easy to Integrate:
    Just replace discord.com with your Vercel domain in the webhook URL. No complicated setup needed!

  • :earth_africa: Globally Distributed:
    Powered by Vercel, enjoy high availability and super low latency no matter where your requests come from. Built on TypeScript.

  • :shield: ToS Compliant:
    Fully complies with Discord’s terms of service, handling rate limits and enforcing anti-abuse measures automatically.

  • :hourglass_flowing_sand: Ratelimit Handling:
    Automatically queue requests with POST /api/webhooks/:id/:token/queue, ensuring smooth operation under Discord’s rate limits.

:video_game: How It Works:

  1. Enter your Discord Webhook URL – Paste in the webhook URL you get from Discord.
  2. Get Your Proxy URL – The proxy service will replace discord.com with your Vercel domain.
  3. Copy & Paste – Simply click “Copy” and use the new URL in your app!
  4. (Optional) – test an API response by visiting your domain.vercel.app/api/test

Screenshot

XQiAphB
XQiAphB1265×846 225 KB

:rocket: Deploy Your Own Proxy!

Ready to get started? Deploy your own version of this webhook proxy for free in a few clicks on Vercel:

Deploy on Vercel

:link: Explore the Source Code

Want to see how it works under the hood or run a local version? Check out the source code on GitHub:

View on GitHub

Acknowledgements

:heart: Inspired by @lewisakura’s Webhook Proxy

Production Build Status:

example workflow

Contributors welcome, and always open to any feedback.

21 Likes
#2

Woops, the current version does not include the /queue endpoint! I will add this back as soon as I can

2 Likes
#3

yo this is awesome, thanks!!!

2 Likes
#4

This is an awesome resource! I had been using lewisakura’s webhook proxy before and was considering creating my own, but you’ve done that for me!

2 Likes
#5

Have you had a chance to add this?

1 Like
#6

image
image769×115 39.1 KB

I’m trying to use this, but it’s causing an error for some reason. I’m requiring the module I’m using for this through a serverscript in serverscriptservice. Is there something I’m doing wrong with the json formatting itself?
When I try to use the Proxima proxy, it sends the embed to discord without issue, but the idea of hosting my own private proxy with seems sounds better to me than using a public one, so I was wondering if there’s anything i can do to fix this?

image
image611×524 32.7 KB

EDIT: i fixed it somehow, i kinda just tried using different data templates i got from devforum posts (for the embed data) until i successfully modified one and it worked

1 Like
#7

Have you tried POSTing data and not finalData?

1 Like
#8

Hi, unfortunately I have not added back this feature yet.

2 Likes
#9

I’m experiencing this same exact issue
also I tried the solution StarVSK mentioned and that didn’t work

1 Like
#10

Hello I think i fixed a issue with how you where handling embeds i am still testing but i will

1 Like
#11

put in a pull request Link to it

3 Likes
#12

Thanks for fixing this! Merged in. I appreciate it

1 Like
#13

also added better logging you can see why it errors and also when its sent

1 Like
#14

Thank you for this fix! Works great after adding it.

1 Like
#15

this looks great but when i try to use it, it just gives me a 401 error/405 error

1 Like
#16

cool but i’m getting error 401 everytime I try and use it

#17

these aren’t error codes that this has?

#18

Amazing, can’t wait for the queue endpoint to be added!

#19

would there be a more proper way of explaining how to implement it then, since i have the website up perfectly fine, but it always just runs the 2 aforementioned error codes