Revoke token
Overview
Revoke the Passport access token presented in the request's Authorization: Bearer header (SSO sign-out). It acts only on the current token.
Prerequisites
- A bearer token. Callable with Partner and Account tokens.
Base URL
| Environment | URL |
|---|---|
| Production | https://production-api.shoutaboutus.com |
| Development | https://development-api.shoutaboutus.com |
Endpoint
GET /api/v1/sso/revoking-token
Authentication
-
Requires a bearer token in the
Authorization: Bearer <bearer-token>header. -
Who can call it: Partner and Account tokens.
-
Authentication uses Passport.
-
The endpoint sits in the admin-only
ssoroute group, but the method itself has no extra role gate. -
It scopes purely to the caller's own presented token.
-
Any authenticated principal (Partner or Account) holding a valid token revokes only that token.
-
No partner-tree walk, no ownership check, no invite hash.
Rate limit
- No rate limit.
Request
- No path params.
- No query params.
- No request body (GET).
Response
data.status(string) — always"success"on success.data.message(string) —"Token revoked successfully!".
On failure the catch path returns defaultErrorResponse (generic error envelope) and writes an emergency debug log.
200 OK · 200
200{ "data": { "status": "success", "message": "Token revoked successfully!" } }Errors
| Status | Meaning |
|---|---|
401 | The bearer token is missing, expired or invalid |
500 | Unexpected server error |
Example request
curl --request GET \
--url "https://production-api.shoutaboutus.com/api/v1/sso/revoking-token" \
--header 'Authorization: Bearer <bearer-token>' \
--header 'Accept: application/json'Updated 11 days ago
