Agreed. I'm chuckling because I was wrestling with this exact same bug on a FastAPI project last night. I caught it because I have a habit of submitting API endpoints multiple times with the same data to see how the database reacts. Got a key collision when I tried to submit the endpoint the second time and figured out that setup didn't create a new UUID each time.
Unit tests are good, yes. Monitoring is also good. But just taking 30 seconds to do some manual testing will catch a LOT of unexpected behavior.
I appreciate it. We both come from data and backend backgrounds, landing page design isn't exactly our strong suit :). Getting some proper design resources brought in for our marketing page is on my todo list after we finish the product.
My cofounder and I started this project to solve issues I had building my own API service. I had built a data API service and then realized I needed a way to service customers. I fell down the rabbit hole of building user onboarding workflows, account recovery, issuing and storing API keys, etc. It ended up being more work than the API itself!
It's the cost of doing business, I suppose. But it was such a pain that I got together with my cofounder and we decided that we should build a company to make that part easier!
If you set up an account with us to sell your API(s), we'll charge $5/month for the account. If you don't make any sales, then the most you'll ever pay out of pocket is the $5.
Once you start making revenue, you'll get a $5 credit towards the revenue share each month. In other words, it ends up being the greater of $5 or 22% of total revenue. Hope that helps!
Thanks for the feedback! And yes, we're charging a 22% revenue share, which represents the all-in fee (no additional processing fees on top of it). I hope you'll find the final product worth it :)
Thank you for the feedback! We're still very early stage right now, and we'll be releasing more specifics around security in the coming days.
RestEasy will operate by forwarding your customer's request to your endpoint, so there will be two keys used to secure the API call. One from your customer to RestEasy, and then one to your service. We'll be doing a detailed writeup on that in the next several weeks.
The domain will be white-labelled, so the API calls will still be going to a subdomain of myawesomeAPI.com
I am cofounding a new SaaS "starter pack", but for a very specific niche. This product aims to serve as the frontend and middleware for anyone planning to launch an API-as-a-Service product. The idea for this product is straightforward: once you've built an awesome API service and are ready to share it with the world, you've only done like 20% of the work. You need to build an entire UI so that your customers can create accounts, issue API keys, set up billing information, keep track of API usage, logging, admin UI's to track all of this, and the list goes on...
Our product, which we're calling "RestEasy", is the 'as-a-Service' to your API. You're going to be able to stand up a completely white-labelled user portal on your own custom URL, complete with your own color scheme and logo. We will also provide white-labelled admin portals so you can manage your users, API keys, pricing, check usage logs, some basic analytics, etc.
Check out the homepage and let me know what you think! Are there any specific use cases you would want to see covered in the platform?
Be sure to sign up for the waitlist. We'll be sending out periodic updates along the way to keep you updated on how we're doing.
Unit tests are good, yes. Monitoring is also good. But just taking 30 seconds to do some manual testing will catch a LOT of unexpected behavior.