Refresh Token
When an access token expires, the user can manually re-authenticate or use the refresh token mechanism to get a new access token.
Request:
POST https://auth.reltio.com/oauth/token| Name | Required | Description | |
|---|---|---|---|
| Headers | Authorization | Yes | Basic authentication header, provided by Reltio with a specific set of client credentials. |
Content-Type | Yes | application/x-www-form-urlencoded | |
| Body Parameters | refresh_token
| Yes | Refresh token retrieved when first obtaining the access token. |
grant_type
| Yes | Type of access token request. Value: refresh_token. | |
Response:
If the refresh token request is successful, the response will contain a JSON object with the same structure as in the original Access Token request.
Request
POST https://auth.reltio.com/oauth/token
Headers:Authorization:Basic cmVsdGlvX3VpOnNlY3JldA==
Content-Type: application/x-www-form-urlencoded
Body: grant_type=refresh_token&refresh_token=676742af-989b-4d40-b7cc-f69ccadd45ea Response
{
"access_token":"204938ca-2cf7-44b0-b11a-1b4c59984512",
"token_type":"bearer",
"refresh_token":"676742af-989b-4d40-b7cc-f69ccadd45ea",
"expires_in":3599,
"scope":"configuration_api entities_api graphs_api groups_api interactions_api relations_api"
}Token API request limit
By default, tokens expire after 60 minutes. To authenticate into Reltio using scripts or integrations, you must get a token, store it, and use it until it expires. Get a new token after the current one expires.
If you don't store your token, you will need to request a token every time you want to authenticate into Reltio. This is a highly inefficient practice. In Reltio, we have a limit of 10 GET token requests per second. If you exceed this limit, you will see the 429 HTTP status (Too Many Request) message. This indicates that you need to change the way you are requesting tokens to ensure it complies with our limit.