Add TRACES credentials

Save TRACES administrator or sub-user credentials for a TAN to use with enriched APIs.

POST /tds/traces/deductors/credential

cURL

Success

curl --request POST \
  --url https://test-api.sandbox.co.in/tds/traces/deductors/credential \
  --header 'Authorization: <authorization>' \
  --header 'Content-Type: <content-type>' \
  --header 'x-api-key: <x-api-key>' \
  --data '
{
  "@entity": "in.co.sandbox.tds.traces.deductor.credential.request",
  "tan": "AHMS45586C",
  "password": "{{password}}"
}
'

200

Success

{
  "code": 200,
  "timestamp": 1788414642383,
  "transaction_id": "45a5d0e7-d428-47c3-906e-b039d0e4e157"
}

Save TRACES credentials for enriched APIs, which manage login and sessions for you. Use the deductor’s TAN in tan for either login.

Login	Request fields
Administrator	Send the administrator’s TRACES password in password. Omit pan.
Sub-user	Send the sub-user’s PAN in pan and that sub-user’s TRACES password in password.

Your workspace can save one credential per TAN. To replace saved credentials, delete the existing credentials, then add the new credentials.

To obtain tokens for vanilla APIs, use Authenticate a TRACES deductor.

Headers

Authorization · string · required

JWT access token. For token-generation steps, refer to the Quickstart Guide.

x-api-key · string · required

API key used to identify and authenticate the client.

Content-Type · string · required

Request body format.

Body

application/json

@entity · string · required

Entity identifier for the request.

tan · string · required

TAN for the TRACES account.

password · string<password> · required · write-only

TRACES password for the sub-user when pan is provided, or for the administrator when pan is omitted.

pan · string

PAN of the TRACES sub-user. Omit to use the administrator account.

Pattern: ^[A-Z]{5}[0-9]{4}[A-Z]$

Response

200

application/json

The TRACES credentials were added.

code · integer · required

timestamp · integer · required

transaction_id · string · required