02 - API Authentication
OVERVIEW
The OAuth 2.0 Client Credentials flow allows a client app to use its own M2M credentials to authenticate when invoking API. To begin, obtain OAuth 2.0 client credentials(i.e., Client ID/Client Credentials) by creating a new OAuth Client Application. To create OAuth Client Application, you have to reach out to open a support case with a request for client credentials. Once you OAuth client is created in Thomson Reuters Authorization Server to represent your application, your application can request an access token from Thomson Reuters Authorization Servers.
Invoking Data Insights API Client Endpoints is a two-step process.
Step 1: Generate Access Token Using Client Credentials
POST | /oauth/token HTTP/1.1 |
Host | auth-nonprod.thomsonreuters.com |
Content-Type | application/x-www-form-urlencoded |
grant_type | client_credentials |
&audience | @Audience |
&client_id | @ClientID |
&client_secret | @ClientSecret |
Sample JSON Response from Authentication Request
"access_token" | eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6Ik1V..... |
"scope" | https://api.thomsonreuters.com/auth/edi.odata.api.user |
Content-Type | application/x-www-form-urlencoded |
expires_in | 86400 |
token_type | Bearer |
Step 2: Invoke Data Insights API With Access Token
After getting the access token, call the Data Insights API by attaching the Bearer token in the authorization header.