Are you a web developer? Have you ever been developing an integration against an OAuth service you don't control?
For security purposes, these tools require you to specify a redirect where they will send your users after a successful OAuth handshake. Oftentimes there are arbitrary rules imposed on these URIs that make it difficult to develop your integration locally.
This tool lets you specify https://redirect-uri.com/ as a redirect uri during development. We will redirect you (along with your OAuth callback parameters) back to your local development environment.
Look, if you don't know why you need this, chances are you don't.
That sounds like a terrible idea. It is also unnecessary as your production system should be reachable without this extra hop.
As I said, you really should not be using this in production. But anyway, I am trying my best not to capture any private information. I don't want your tokens either.
Just a few of the rules that I have encountered as a developer:
There are a lot of useful and worthwhile solutions to this problem. I decided to go with this one.
I made this service for two reasons: (1) the equivalent I was using had a bug that I couldn't get around and; (2) it sounded like fun weekend project.