DELETE
/v1/me/tokenEnds the token in the Authorization header and nothing else. Other devices stay
signed in.
Needs no scope. A credential may always destroy itself, whatever else it was or was not allowed to do, so a client that asked for a very narrow token can still sign out cleanly.
Request
curl -X DELETE https://api.proppertrading.com/v1/me/token \
-H "Authorization: Bearer ptat_9f2c1a44_3b8e7d2f5c9a1b4e6d8f0a2c4e6b8d1f"
Response
204, no body.
Delete the token from the device's own storage as well. The server has forgotten it either way, but a client holding a dead secret will spend a request finding that out on every launch.
Errors
| Status | Code | Meaning |
|---|---|---|
| 401 | invalid_token | Not a token, or the secret does not match |
| 401 | revoked_token | Already signed out. Nothing left to do |