Skip to main content
Migrate API applications to Thomson Reuters Account
Search
Search Account management Support Help and Support.

This article applies to:

  • Product: ONESOURCE Platform

Prepare for API application changes

Prepare an API application for migration from Apigee-based authentication to Thomson Reuters Account (Auth0)-based authentication.
Complete the following steps whether you migrate from an existing application or onboard a new one.
  1. Decide which authentication method fits each application.
    1. Select
      Client Credentials
       or
      Client Assertion
       for machine applications.
      Client Credentials uses a shared secret; Client Assertion uses a key pair.
    2. Select
      Authorization Code
       for user applications. PKCE is mandatory, with no exceptions.
      note
      If you already use Client Assertion today, Thomson Reuters Account automatically reuses your registered public key. It sets up your Thomson Reuters application for you. You can change the certificate afterward.
  2. Review your current API applications, then select your upgrade path.
    Upgrade an existing application in place, or create a new Thomson Reuters application and cut over. After you upgrade an application, you can't revert it to Apigee-based authentication.
  3. Plan for the credential change.
    You become responsible for managing and rotating your Client Secret. We recommend rotating it at least every 12 months.
  4. Review guidelines before you migrate.
    Cache your tokens and respect the rate limit of 40 token requests per hour, per client. This keeps Thomson Reuters from rate-limiting or blocking your integration after the change.

Related Content