Revoke connection
Revoke Hyperspell’s access to a provider and delete this user’s stored data.
The external OAuth/Unified revoke and the (potentially large) data purge run in
a background Temporal workflow; this returns 202 Accepted immediately. A
heavy provider — a Gmail account can carry hundreds of thousands of chunks —
plus a slow third-party revoke would otherwise outrun the request timeout: the
old synchronous path “timed out” for the caller while still finishing
server-side, making the outcome invisible. Idempotent per (app, user, provider).
Authorizations
API Key or JWT User Token. If using an API Key, set the X-As-User header to act as a specific user. A JWT User Token is always scoped to a specific user.