revokeCustomerToken mutation

The revokeCustomerToken mutation revokes the customer's token. It returns true if the token was successfully revoked.

We recommend you specify a customer token in the header of your call. However, you also can use session authentication.

Syntax

mutation {
  revokeCustomerToken {
    RevokeCustomerTokenOutput
  }
}

Reference

The revokeCustomerToken reference provides detailed information about the types and fields defined in this mutation.

Example usage

The following call revokes the customer's token.

Request:

mutation {
  revokeCustomerToken {
    result
  }
}

Response:

{
  "data": {
    "revokeCustomerToken": {
      "result": true
    }
  }
}

Errors

Error
Description
The current customer isn't authorized.
The current customer is not currently logged in, or the customer's token does not exist in the oauth_token table.