Configure apigee endpoints

The Configuration Sync and Transaction Sync failed because the API rate limits were too low and some access settings were incorrect. This article defines a standardized implementation process to prevent similar failures. It provides step-by-step instructions for the Determination Anywhere (DA) implementation team to create a machine application user and configure API rate limits on Apigee endpoints.

Assess the environment

Before you make changes, verify the environment:
  • Verify the target environment (UAT or production).
  • Review current API rate limit configurations.
  • Validate tenant or company scope requirements.
  • Document current settings for potential rollback.
  • Ensure the API Administration tile is active for the designated tenant.
After your assessment is complete, sign in to the ONESOURCE Platform for your environment to access the Apigee console:

Create a machine application user

Refer to Authorization for ONESOURCE API on the Developer Portal and complete step 1 to create a machine application user. When you select scopes for ONESOURCE products, select the option for your environment:
  • AWS (AMER): urn:tr:onesource:auth:api:indirecttaxdetermination
  • OCI: urn:tr:onesource:auth:api:indirecttaxdeterminationiv

Assign a role

Assign the
Cloud Sync User
role to the machine application user. This role enables synchronization with the DA Mothership and helps prevent 401 Unauthorized errors during sync.

Recommendations for rate limit configuration

Recommended per-tenant/company limits:
  • UAT: 5,000 requests
  • Production: 5,000 requests
If you need increased limits based on data volume, email the
DBProvision team
at dbprovision.corporates@thomsonreuters.com.
Include:
  • New rate limit requirements (based on expected data volume).
  • The name of the product in scope (refer to scopes in the previous section).

Related Content

  • API
    Format: Article, 1 min read