Resume a paused subscription
Delivers the events that reach the hub after the resume, and only those. It also clears the failure history, so the paused time never counts toward auto-disable. For a pull subscription, the read position moves to the newest event. Each empty read while paused also moves it, so the events it had not read yet are skipped. ?after= still reads older events within retention. This route is naturally idempotent and requires no X-Idempotency header: resuming a subscription that is not paused returns 200. A subscription that the hub stopped answers 409 subscription_stopped_by_hub: call POST /v1/subscriptions/{id}/verify instead. verify never resumes a paused subscription.
Authorizations
A bearer JWT issued by Access Manager. The /v1 surface never reads a tenant from the body, path, or query. Machine callers obtain a token with the Access Manager client-credentials flow. The /admin surface authorizes against an operator scope and carries no tenant context.
Path Parameters
The unique identifier of the subscription (UUIDv7).
Response
Done, or already in that state (no body).

