Z-Connect

Agent Device Changed

Documentations

Documentations for API

End Points

https://z-sandbox.jsbl.com/zconnect/api/v1/agentdevicechanged

Http Method

POST

Header

Name	Type	Values	Description
clientSecret	TEXT	Access-Token	Auth2.0 verification
Accept	JSON	application/json	application/json
Content-Type	JSON	application/json	application/json
clientId	TEXT	*************	*************
organizationId	TEXT	223	Authenticate organization

Request Parameters

Name	Description	Required	Parameter Type	Length	Sample Value

Sample Request

{
    "agentDeviceChangedReq": {
        "DTID": 5,
        "PIN": "PLVIaH17OCzFw94Ze1wpZg==",
        "UDID": "d203c723645b31a3",
        "ENCT": 1,
        "UID": 1063683,
        "USTY": 3,
        "ACTION": 0
    }
}

Response Parameters

Name	Description	Parameter Type	Length	Sample Value

Response Sample

{
  "agentDeviceChangedRes": {
    "id": "-1",
    "errors": [
      {
        "code": "9028",
        "level": "3",
        "message": "Your OTP is not valid. Please enter the correct OTP.",
        "THIRD_PARTY_TRANSACTION_ID": "",
        "nadraSessionId": ""
      }
    ]
  }
}
Respo

Response Code Details

{
  "agentDeviceChangedRes": {
    "id": "-1",
    "errors": [
      {
        "code": "9028",
        "level": "3",
        "message": "Your OTP is not valid. Please enter the correct OTP.",
        "THIRD_PARTY_TRANSACTION_ID": "",
        "nadraSessionId": ""
      }
    ]
  }
}
Respo

{
    "messages": "Bad Request - Invalid Access Token",
    "errorcode": "4001"
}

{
    "messages": "Bad Request - Invalid Request Payload",
    "errorcode": "4002"
}

{
    "messages": "Bad Request - Invalid Authorization Header",
    "errorcode": "4003"
}

{
    "messages": "Something Went Wrong",
    "errorcode": "4004"
}

{
    "messages": "Record Not Found",
    "errorcode": "4005"
}

{
    "messages": "Invalid Client Id\/Secret",
    "errorcode": "4006"
}

{
    "messages": "Bad Request - Invalid Access Token",
    "errorcode": "4007"
}

Try out yourself

Security

X-IBM-Client-Id(apiKey located in header)

X-IBM-Client-Secret(apiKey located in header)
1c48aa28-2614-486f-aa2c-cbc86cc7ab51

Header Parameter

Name	Values	Description
Content-Type	application/json	Content Type application/json is supported
Accept	application/json	Content Type application/json is supported
organizationId	xyz	You will make a call to the auth-blb api and give it your client ID. You should add the client secret and organisation ID it returns here.
clientId		Enter your verified Client Id
clientSecret		Enter Your Verified Client Secret