Logout
Ends the session of a token that Login gave. From then on, every call with that
token answers Token invalid or expired. Sign a token out when the integration no longer needs it,
for example when a scheduled run that signed in has finished, or when the token may have leaked.
Other tokens of the same user are not affected. How tokens end on their own: Token expiry.
POST /api/v1/LogoutToken: your-tokenThe request has no body: the token to sign out is the one in the Token header.
| Rule | Info when it fails |
|---|---|
The request has a Token header. |
Token missing in header |
| The token is a TrakIT token whose session has not ended. | Invalid Token, Invalid Token Split, Token invalid or expired |
| The user is not locked. | User account is locked |
Logout works even when the user no longer has API access, or
when the user’s password has expired.
Response
Section titled “Response”On success, Code is 1 and Info is Signed out.
{ "Code": 1, "Info": "Signed out", "RetInfo": null, "RowsAffected": 0, "Scalar": null, "Identity": 0}- The session stays on the user’s Session Log tab, with
Last Access at the time of the
Logout. - TrakIT logs every
Logoutcall with the user.

