Skip to main content
POST
/
tds
/
compliance
/
csi
/
otp
Generate OTP
curl --request POST \
  --url https://api.sandbox.co.in/tds/compliance/csi/otp \
  --header 'Authorization: <authorization>' \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <x-api-key>' \
  --data '
{
  "@entity": "in.co.sandbox.tds.compliance.deductors.otp.request",
  "tan": "<string>",
  "mobile_number": "<string>",
  "from": 123,
  "to": 123,
  "consent": "<string>",
  "reason": "<string>"
}
'
{
  "timestamp": 1731669661517,
  "transaction_id": "166148b8-25e3-4ef2-b052-5a27098ebb0e",
  "data": {
    "@entity": "in.co.sandbox.tds.compliance.deductors.otp.response",
    "tan": "AHMA09719B",
    "mobile_number": "1234567890",
    "from": 1722450600000,
    "to": 1730313000000,
    "reference_id": "FOS005981930273",
    "message": "OTP sent successfully"
  },
  "code": 200
}

Headers

ā€‹
Authorization
string
required

JWT access token

ā€‹
x-api-key
string
required

API key for identification

ā€‹
x-api-version
string

Body

application/json
ā€‹
@entity
enum<string>
required
Available options:
in.co.sandbox.tds.compliance.deductors.otp.request
ā€‹
tan
string
required

TAN of deductor/collector. Regular Expression: [A-Z]{4}[0-9]{5}[A-Z]{1}

Pattern: [A-Z]{4}[0-9]{5}[A-Z]{1}
ā€‹
mobile_number
string
required

Mobile Number to send the OTP. Pattern: [1-9]{1}[0-9]{9}

Pattern: [1-9]{1}[0-9]{9}
ā€‹
from
integer
required

Date from which challan details are to be fetched. Value in EPOCH timestamp

ā€‹
to
integer
required

Date till which challan details are to be fetched. Value in EPOCH timestamp

ā€‹
consent
string
required

Consent of the end-user to get their information. Possible values: Y or y

ā€‹
reason
string
required

Indicate the purpose. Min length: 20 characters

Response

200 - OK

ā€‹
timestamp
integer
ā€‹
transaction_id
string
ā€‹
data
object
ā€‹
code
integer