Tokens and Permissions
Refresh token
Generates a new token value; the old token value becomes immediately invalid. Any token can refresh itself, except a read-only personal access token; refreshing another token requires the canManageTokens permission.
The decrypted token value is returned when refreshing a non-master token, the token used for authorization, or when the project has a dedicated project feature enabled.
post/v2/storage/tokens/{id}/refresh
Request
- Base URLhttps://connection.keboola.com
- Auth
- API key in header X-StorageApi-Token
- or API key in header X-KBC-ManageApiToken
- or HTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
idinteger required
A valid token ID. You can get it from the Token verification call.
Response
Refreshed token.
Example response
{
"id": "484",
"created": "2017-02-13T12:01:05+0100",
"refreshed": "2017-02-13T12:01:05+0100",
"description": "my-new-token",
"uri": "https://connection.keboola.com/v2/storage/tokens/484",
"dailyCapacity": 5,
"token": "75-12d4bfa4995694a1c956e7bb1eea0df5cc53acdb",
"creatorToken": {
"id": 1,
"description": "dev@keboola.com"
},
"componentAccess": [
"keboola.ex-db-mysql"
],
"bucketPermissions": {
"in.c-main": "read"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.