All requests to the Redivis API require a valid access token. You can create access tokens by navigating to your workspace/settings and scrolling to the bottom of the page.
When you create a token, you will have the ability to name it and grant it specific scopes; these can also be modified later. When the token is created, you will be able to see it once — store the token in a secure place for future use.
Scopes allow for you to control what actions any given token may perform. It is highly recommended to limit the scope of a token to the minimum necessary for it to function. The following scopes may be provided on access tokens:
This is the default scope, and is present on all tokens. It only allows access to resources on Redivis that are publicly available (e.g., if you were logged out). Access tokens that only have the public scope can be safely shared with others, and are useful for building integrations that need to avoid leaking any restricted content.
Allows for "overview" access to datasets that you can see but are hidden to the general public. This will reveal the dataset's existence and some documentation, but will not provide access to restricted variable names, summary statistics, or data.
Allows for "metadata" access to datasets whose metadata you can view but are hidden to the general public.
Allows for access to a dataset's raw data when it is visible to you but hidden to the general public.
In order to interact with the API, you will need to provide your token in the header of your HTTPS request.
Set the token in the
Authorization request header with the value
Bearer ACCESS_TOKEN .
curl -H "Authorization: Bearer $ACCESS_TOKEN" "https://redivis.com/api/tables/:tableId"
If you have lost an access token, are no longer using it, or if you have reason to believe your access token has been compromised, it is important that you revoke it. Navigate to your workspace settings and press the "revoke" button next to the token in question.