ObtainKrakenJSONWebToken
The unifying approach used to get a Kraken token (JWT: JSON Web Token) with different types of input.
The currently supported inputs are: - account user email/password combination - account user API key - organization live secret key - pre-signed key - refresh token
Fields
The body payload of the Kraken Token. The same information can be obtained by using JWT decoding tools on the value of the token field.
Field with the possible errors of the query/mutation.
Please use the 'possibleErrors' query or the 'X-Kraken-Possible-Errors' header instead.
- Marked as deprecated on 2025-01-31.
- Scheduled for removal on or after 2025-03-01.
A Unix timestamp representing the point in time at which the refresh token will expire.
A token that can be used in a subsequent call to obtainKrakenToken to get a new Kraken Token with the same access conditions after the previous one has expired.
The Kraken Token. Can be used in the Authorization header for subsequent calls to the API to access protected resources.
Example
{
"payload": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType,
"refreshExpiresIn": 84,
"refreshToken": "spring-model-next-such-ok",
"token": "mind-air-woman-yard-sea"
}