Hey DEV community ๐
Iโm Mark, an indie dev whoโs spent years building backend systems for SAAS products, messaging platforms, finance tools, and a lot of client projects.
And over time, I noticed that I kept rewriting the same micro-services over and over.
Things like:
Shortening a URL
Generating a QR code
Creating secure tokens or vouchers
Storing a small image / blob
Managing structured chat/dialog flows
Most projects needed some combination of these.
So I finally decided to turn that repetitive work into a standalone project.
๐ Introducing myapi.rest
Itโs a unified API toolkit that bundles common developer utilities behind one simple REST interface.
Instead of juggling 5โ10 different providers, everything lives under one clean, consistent API.
Whatโs built so far:
๐ URL Shortener (57 trillion shortcode space + analytics)
๐งพ QR Code / Barcode Generator
๐ผ๏ธ Image / Hosting
๐ Token / Coupon Generator (in progress)
๐ฌ ChatFlow Logic API (in progress)
All respond with clean JSON, fast responses, and straightforward endpoints.
๐ง Why I built it
As an indie dev, I wanted something:
reusable
consistent
fast
with one API key
and a single dashboard
Basically, a โutility layerโ I could plug into any new SaaS, app, or script without rebuilding everything again.
And I figured other devs might want the same.
๐ฌ Looking for honest feedback
Iโd really appreciate thoughts from the DEV community:
Would a unified API toolkit like this be useful in your own dev workflow? Or do you prefer using individual providers?
Is bundling multiple utilities together a good idea, or too broad?
What other small APIs do you find yourself rewriting often? I want to add more modules over time.
What developer QoL features matter most?
Examples: better docs, SDK examples, analytics, faster endpoints, etc.
๐ค If anyone wants to see the project it's here https://myapi.rest
Iโm happy to share more details or answer questions.
Just curious what other indie devs think about this approach.
Top comments (0)