Don't wait on that export to arrive. The API will hand you the same list today, and it comes with a catch that matters more than the export bug does.
The endpoint is GET https://api.statuspage.io/v1/pages/{page_id}/subscribers, and it takes a type filter, so you pull email and sms separately. There's also /subscribers/count, which is the honest check on whether your pull is complete.
Here's the catch. A subscriber who bounces gets quarantined, in the docs' words "If a (page or component) subscriber fails to receive a notification, they will be quarantined", and then this: "Quarantined subscribers are excluded from API responses and interactions by default." So a straight pull silently leaves them out. On a normal day that's tidy. When you're moving everyone off a system that's being switched off, the people who bounced once are exactly the ones you can't afford to drop, and the response gives you no hint they're missing.
The fix is the state parameter, which "only return subscribers in this state" and takes "all" to "find subscribers in any states". Three states show up in the schema, active, quarantined and unconfirmed, so ask for state=quarantined directly. That names the population for you, and a zero means you genuinely have none.
There's a separate /subscribers/unsubscribed list too. Pull it if your migration needs to honour prior opt-outs instead of re-subscribing people who already left.
None of this tells you why your export email never arrived, and that part needs a support ticket, since only they can see the send logs. But you don't have to be blocked on it in the meantime.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.