Building a starter pack for an API-as-a-Service
resteasyapi.com
Building a starter pack for an API-as-a-Service
1–10 of 28 posts
Re: Building a starter pack for an API-as-a-Service
#2I 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.
[Website Link](https://www.resteasyapi.com/)
Re: Building a starter pack for an API-as-a-Service
#3Very cool, I've been thinking about the need for a service like this.
Does the 22% fee you're charging mean a 22% revenue share of what the customer pays? If so... that's very expensive.
Re: Building a starter pack for an API-as-a-Service
#4I'm using Deno's SaaSKit for this: https://github.com/denoland/saaskit
Re: Building a starter pack for an API-as-a-Service
#5I sell an API as a service,[0] and I've been using RapidAPI for years. I've never been happy with them. They charge a 20% fee, and then there's another 3-5% fee for payments via PayPal. And they do many small transactions per month, so you pay PayPal's minimum fees over and over, making the total fees about 25-30%.
On top of that, their service is terrible. Customer support is rarely helpful, they frequently fail to bill my customers and just shrug it off, their dashboard takes 20+ seconds to load simple views. I could go on and on.
I welcome competitors in this space because I've been surprised at how few vendors offer what I'd expect to be not so hard a service.
The thing that kills this deal for me is that RestEasy isn't the merchant of record, so the API owner still has to figure out how to pay taxes in every state/country where they're liable for taxes.
The other thing that would make me nervous is that you're a brand new company, and you're a point of failure for my API. If RestEasy goes down, my service goes down.
RestEasy's site also currently has a lot of typos, which would also make me nervous about betting my uptime on this service.
I'm currently in the process of migrating to Paddle. They act as merchant of record, and their fees are 5%, though they require me to write a lot of my own custom code to integrate with their system.
Re: Building a starter pack for an API-as-a-Service
#6> Pricing
> $5/month per organization
> 22% fee for paid endpoints
> $5/month fee credit
How does this work ?
Re: Building a starter pack for an API-as-a-Service
#7I sell an API as a service,[0] and I've been using RapidAPI for years. I've never been happy with them. They charge a 20% fee, and then there's another 3-5% fee for payments via PayPal. And they do many small transactions per month, so you pay PayPal's minimum fees over and over, making the total fees about 25-30%. On top of that, their service is terrible. Customer support is rarely helpful, they frequently fail to…
Tying in paddle as merchant of record for all installs shouldn’t be that challenging no?
Stripe has connect as well to split but I’m not sure their merchant of record features are as mature.
Re: Building a starter pack for an API-as-a-Service
#8If I were building an API service, I think I would want control over the security around the API and the site doesn't describe in depth how the actual customer's data is secured, just "assign a random token".
What domain would this white-label admin interface reside on if a sales/signup page and my actual API endpoints are on my domain for example? Wouldn't customers find it jarring to be going to "myawesomeAPI.com" to signup and then the domain for actual API calls ends up on "resteasyapi.com"?
Re: Building a starter pack for an API-as-a-Service
#9Very cool, I've been thinking about the need for a service like this. Does the 22% fee you're charging mean a 22% revenue share of what the customer pays? If so... that's very expensive.
Thus sounded really interesting, right up until I saw 22% - that is a lot.
Re: Building a starter pack for an API-as-a-Service
#10I 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 cre…
So there is no actual functionality to try out right now? From what I browsed, the site is essentially a landing page + email signup.