Sign in
Session Authentication

Logging out / Revoking an App User

Logging out is not strictly necessary for Web Users; all sessions expire 24 hours after they are created. But it can be a good idea, in case someone else manages to steal your token. It is also the way Public Link and App User access are revoked. To do so, issue a DELETE request to that token resource.

Revoking an App User

The token associated with an App User is actually just its Session Token. As a result, although an App User Token can uniquely be used as a URL prefix as described here, the session associated with it can be revoked in exactly the same way a session is logged out, by issuing a DELETE request to its Session resource.

Note, however, that an App User cannot revoke itself; a User must perform this action.

delete/v1/sessions/{token}

Path parameters

tokenstring required

The session bearer token, obtained at login time.

Response

OK

successboolean required

Example response

{
  "success": true
}

Changes

Changed in 3 of the 54 revisions of this API.4

  • 022694254f0d1See the full diff
    • ○

      api operation id Revoking an App User removed and replaced with revokeAppUser

      api-operation-id-removed

  • b11b54eea4871See the full diff
    • ○

      removed the non-success response with the status 403

      response-non-success-status-removed

  • e8c2858fd4eb2See the full diff
    • ○

      api operation id revokeAppUser removed and replaced with Revoking an App User

      api-operation-id-removed

    • ○

      added the non-success response with the status 403

      response-non-success-status-added

    This revision also has 11 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog