Whatssaapi?

I’ve keep paying for SaaS tools but refusing to use them.

Here’s what I do instead. 

1. Grab a bearer token from Chrome DevTools.

2. Map the endpoints with Claude/Codex.

3. Do exactly what I want, directly through the API.

I used to waste hours fumbling through interfaces. Now I get instant answers: it either works, or there’s no endpoint.

APIs do lot’s of things that aren’t supported by the web app.

• undelete items

• use exact values instead of presets (i.e. in time ranges)

• better search params

When I don’t like part of the service, I replace it!

I use an AI SDR to automate outbound, which has 4 steps:

1. Find profiles

2. Enrich them (get contact info, etc)

3. Generate custom messages

4. Send messages

Everything is great except Step 3. I hate the custom messages. They’re cringey and don’t sound like me.

So I rebuilt it!

I still let the service handles steps 1 and 2 (find and enrich profiles). 

Then I get the profiles through the API, and generate the custom messages using my own logic. 

I upload my messages with the API and let the service takes back over for Step 4.

It’s the natural interaction pattern now that we have coding agents. 

Interfaces are becoming a hindrance; they’re hard to build, tedious to maintain, and confusing to users. They expose only a small slice of the underlying business logic, and you can’t replace parts you don’t like.

Software will become APIs, not apps. Software-as-an-API. That’s what’s SaaAPI.

-Tim L