![]() |
API Documentation
|
POST - used to obtain for an access token (and optional refresh token) representing a Covata user (typically within an organization) using either the authorization code or password OAuth 2.0 grant types.This API endpoint serves a number of purposes:
The request's header requires HTTP Basic authentication, whose value is the string value of your application's client ID and client secret (separated by a colon) and encoded with Base64.
Note: The client ID and client secret values constitute your application's client credentials, which would have been generated when your application was registered on the Covata Platform. Also see Configuring client applications in the Safe Share Administrator's Guide for more information.
For example, encoding:
exampleClientApplication:exampleClientApplicationSecret ZXhhbXBsZUNsaWVudEFwcGxpY2F0aW9uOmV4YW1wbGVDbGllbnRBcHBsaWNhdGlvblNlY3JldA==Therefore, the HTTP Basic authentication header would be:
Authentication: Basic ZXhhbXBsZUNsaWVudEFwcGxpY2F0aW9uOmV4YW1wbGVDbGllbnRBcHBsaWNhdGlvblNlY3JldA==The request also requires form URL-encoded data in the body:
Content-Type: application/x-www-form-urlencodedThe following required parameter must be sent in the body of the request (as form URL-encoded data):
password for the password grant type authorization_code for the authorization code grant type. In addition to the required parameters above, some of the following parameters are also required based on the grant type used and should be included in the body of the request (as form URL-encoded data):
password ( Required when using the password grant type ) - The password of a Covata user's credentials (acquired through your application).
Example (request parameters - using the password grant type):
A JSON-formatted response containing the following members:
bearer. jti - The UUID value for the JWT access token issued in this response. This value is a unique ID for the JWT issued in this response and is also known as a JWT ID.
Example (response):