wrapi.io

API-Wrapping-as-a-Service

Visit Website
January 1, 2021 #buildinpublic

Found out that #buildinpublic is a thing. And I really loved it! Building stuff, getting motivated by people which are also build stuff, pushing progress and talk about your product? Perfect stuff. So I've created a Twitter account for wrapi.io and kept tweeting.

I've also created the visual brand for that purpose. Created a character as Brand and to personify wrapi.io which is a burrito. I think that's a funny idea! Had a lot of fun doing it that way. It just felt natural and friendly. Also now I have a bridge to every wrap / burrito shaped food, so prepare for some food'n'API-porn on wrapis twitter.

Comment

October 10, 2020 Fast forward to the "real commitment"-part

Right after I finished a big project and gained a new slot for a side project I finally choose wrapi.io to be my next thing. This was also the time where I came up with the actual name of this product: wrapi and ofc. buyed an *.io domain. So yeah. Say hello to wrapi.io. Literally "Wrap API".IO. IO is more or less also unofficially known as "Input/Output". So quite matching, isn't it?

Comment

June 27, 2020 Imagine a MVP. But with even lower expectations.

After some evenings I had basically the backend mocked. An API wrapper which can be created & configured by an JSON file. So it accepts a project configuration as input and does it's magic. ✨
Which this bare minimum of functionalities I was able to wrap & integrate third party APIs in minutes. But I want seconds!

Comment

June 12, 2020 First commit 💪

So, I shouldn't have started that early, 'cuz you know. Yet another Side Project! And I had tons of projects that time. But guess what?

Maaaaaybe I could write just a little bit code. Just enough to use it in a rough way. Only the core functionalities. Just to make it work for my current projects. A little proof of concept, so to say. Not that I wanted to work on this urgently, you know? 😂

Comment

June 1, 2020 The moment the idea came

I was writing some code.. wrapping an API. Again. Have done this a bazillion times! But every project requires it's own unique API and logic. Than it hit me. mindblown.gif What if there was a Service which could wrap any API with the flexibility of a handwritten API? What if it's the gateway for a tons of integrations with other #NoCode / #serverless / #webhook tools?

I don't know, this Idea kept me RESTless hahah.

Comment

About

As a developer I love tools which makes people lives easier. And as a developer I wrote tons of API wrappers. I got sick of writing API wrappers! Especially for side projects. So this has to be a good SaaS, right?