Authentication
To ensure secure data transactions, Validere"s Public API uses a secure OAuth 2.0 authorization process for accessing its API. Clients must obtain an auth0 client_id
and client_secret
from our technical support team, which is then used to retrieve a machine JWT token for API access.
Steps for Authentication:
Obtain Credentials: Contact our Data Services Consulting team to get your
auth0 client_id
andclient_secret
.Retrieve JWT Token: Use these credentials to obtain a machine JWT token from auth0.
API Access: Authenticate to the Public API using the JWT token as a Bearer token in your requests.
OAuth 2.0 Token Retrieval
Endpoint: To obtain your JWT token, use the Auth0 endpoint:
POST https://validere.auth0.com/oauth/token
Client Credentials: To get your
client_id
andclient_secret
along with the requiredaudience
, please contact a member of our technical support team.Successful Outcome: A successful request will provide you with a JWT token, which you should use as a Bearer Token in subsequent API calls.
Request Details
Headers
Content-Type:
application/json
Body
Format: raw (json)
Example JSON Payload:
{
"client_id": "<client-id>",
"client_secret": "<client-secret>",
"audience": "https://validere360.com/api",
"grant_type": "client_credentials"
}
A bearer token can be generated using the new credentials by making the following api request:
Example usage
curl -X POST "https://validere.auth0.com/oauth/token" \
-H "Content-Type: application/json" \
-d "grant_type=client_credentials" \
-d "client_id=<client-id>" \
-d "client_secret=<client-secret>" \
-d "audience=https://validere360.com/api"
Note: Replace <client-id>
and <client-secret>
with the credentials provided by Validere
Example response
{
"access_token": "your-access-token",
"scope": "some-scope",
"expires_in": 86400,
"token_type": "Bearer"
}
All subsequent requests require providing the bearer token as part of the Authorization
header
curl -X POST "https://app.validere.io/some-api" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer {your-access-token}"
Last updated