Skip to main content

UAT API credentials for EDTS API users

Updated

V3 users (https://edts.ezedistributor.com/api/EdtsV3/) can now generate UAT (test) credentials directly in DingConnect portal and use the test credential to call EDTS API endpoints in UAT mode.

 

Credential limits

  • You can have up to 3 live credentials and 1 test credential at the same time.
  • If you already have more than 3 live credentials, you may continue using them without any changes.

 

How to create a Test Auth Password (UAT credential)

Prerequisite: You must be a Technical Administrator in DingConnect portal. (Please contact partnersupport@ding.com  in case you don’t have access)

  1. Log in to DingConnect portal.
  2. Confirm your role is Technical Administrator.
  3. Navigate to: Account Settings → API → API Security Configuration
  4. Toggle Test ON to generate an Auth Password (UAT credential).
    • Enter a Friendly Name and click New API Password after toggling Test.

      dingconnect pic1.png


      Once the test credential is generated, you can invoke API methods using this credential and receive UAT-appropriate responses. 

 

UAT behaviour notes

  1. Account-number based methods (e.g., GetProducts, GetAccountLookup): 
    • These methods using filter “?AccountNumber=” returns an actual response for any real/valid number.
    • For non-valid account numbers, the API attempts to detect the country from the provided account number and returns the first provider from that country. 
    • This behaviour applies to methods that filter by account number, such as: 
      • GetProviders 
      • GetProducts
      • GetAccountLookup

         
  2. SendTransfer (UAT error simulation):
    • For SendTransfer, every valid number returns a UAT success.
    • To reproduce errors, use the UAT number returned in GetProducts response where the last digits match the mapping in the table (examples: 0000X, 000XX). 
    • You can use any UAT number that matches the pattern—the example below shows a convenient set for an India UAT Number 910000000000: 
Phone Number Error Context
910000000001 RateLimited  
910000000002 TransientProviderError ProviderTimedOut
910000000003 TransientProviderError ProviderRefusedRequest
910000000004 ProviderError ProductUnavailable
910000000005 AccountNumberInvalid ProviderRefusedRequest
910000000006 TransientProviderError ProviderTemporarilyUnavailable
910000000007 InsufficientBalance  
910000000008 AccountNumberInvalid AccountNumberFailedRegex
910000000009 ProviderError RechargeNotAllowed
910000000010 TransientProviderError AccountTemporarilyUnavailable
910000000011 ProviderError ProviderUnknownError
910000000012 OtherError  

 

3. Throttling / Rate limits (UAT)

Please note throttling is applied for all methods when using test credentials.

  • Throttling aligns with DingConnect (DC) API rate limits, except the following methods which are limited to 100 requests per day for UAT traffic:
    • GetProviders
    • GetAccountLookup
    • GetProducts
    • SendTransfer
    • GetPromotions

Important: The limit is per distributor (not per API key), and throttling is only applied for UAT traffic.

 

 

 

Related articles