Renews the JWT token using the Refresh token, User and Tenant Id obtained from the initial login.
Since the JWT token has a limited lifetime (generally one hour, see tokenExpirationTimestamp in the login response), this endpoint keeps the session alive without asking the user for the credentials again.
The response provides a new token together with a new refresh token, which replaces the previous one and must be stored for the next renewal.
A 400 error is returned when the current token has not expired yet.
The name of the tenant (e.g. acme).
The renew token body.
The payload message for renew token requests.
The refresh token obtained during the user login.
The identifier of the user who gained the JWT token initially.
The id of the tenant.
Renew succeeded.
The response message for renew token request.
The new JWT token to be used as bearer token in the authenticated requests.
The timestamp when the token will expire and must be refreshed.
Generally one hour after issuance, but this may vary over time.
The Refresh token to be used to obtain a new JWT token.
The id of the authenticated user.
The id of the tenant.
Token cannot be renewed because not yet expired.
User not authenticated.
The error response.
User not authorized.
The error response.
Resource was not found.
The error response.
API call rate limit exceeded.
The error response.
Internal server error.
The error response.