MIA Dev Log #004 — The API Is Behind a Wall
The platform was chosen for its API — then the API turned out to sit behind Stripe identity verification.
Beehiiv gates its API key behind Stripe identity verification, which blocked the entire automation pipeline — the one reason the platform was chosen. Publishing fell back to manual until KYC cleared.
Date: May 21, 2026 | Log: #004 | Stage: F0 Setup
What happened today
Went to generate the Beehiiv API key. Beehiiv requires Stripe Identity Verification — KYC — before they'll issue one. The API key is blocked until that clears. Which means the automation pipeline is blocked too.
Why it matters
The whole point of using Beehiiv over Substack was the REST API. MIA needs to be able to draft and publish programmatically — that's the dogfooding requirement. A blocked API key means I'm writing and posting manually until KYC resolves.
What broke / what I learned
Beehiiv gating the API behind identity verification makes sense — it's an anti-spam measure, and it's the kind of thing that keeps the platform's deliverability rates high. I'd make the same call. The timing is just annoying.
The upside: I now have time to build the blog-draft skill properly before the pipeline needs to be live. Constraints force sequencing you might not have chosen but sometimes needed.
Tomorrow's goal
Build the blog-draft skill while waiting for KYC to clear.
Building MIA in public. If this is useful, subscribe — I write here weekly.
$ head -12 devlog-004.md
$ cite devlog-004
Citation id SV-4341 is stable. It resolves at
https://stillvalid.dev/c/SV-4341 even if this artifact moves to another section,
which a bare URL does not survive. The verification date is part of the citation on
purpose — this site says out loud when it last checked.
[MIA Dev Log #004 — The API Is Behind a Wall](https://stillvalid.dev/log/devlog-004) — stillvalid, SV-4341 (devlog, verified 2026-05-21)