Check Link Status

introduction check instant link status is used to determine whether instant link was completed with or without carrier authentication, whether the link was clicked within the expiration time, and whether the input device was where the link was clicked this api allows you to periodically check the status of the user's verification process the check instant link should be called at regular intervals, such as every 10 seconds, within a 5 minutes window after the send instant link api has been called after this 5 minute period, the sms link will become invalid, and further attempts to poll will not yield any results it is important to note that the requestid and sessionid parameters are obtained from the response of the send instant link api make sure to retrieve and use the correct values associated with the specific user verification session remember to adhere to the recommended polling frequency and time window to maintain the verification process's efficiency and accuracy api details need to pass the following information "requestid" and "sessionid" are generated from send instant link api requestid sessionid sample curl curl location 'https //api signzy us/api/v3/us kyc/poll check verify/request/\ requestid/session/\ sessionid' \\ \ header 'content type application/json' \\ \ header 'authorization \<auth token>'curl location 'https //api preproduction signzy us/api/v3/us kyc/poll check verify/request/\ requestid/session/\ sessionid' \\ \ header 'content type application/json' \\ \ header 'authorization \<auth token>' request body parameters parameter data type required description requestid string yes unique identifier associated with this request must be unique for each transaction sessionid string yes unique identifier associated with session of this request must be unique for each transaction response body parameters parameter data type description t ransactionid string unique transaction identifier used to identify the results of the request l inetype string line type associated with the phone number possible values are mobile, landline, fixedvoip, nonfixedvoip phonenumber string the phone number of the originating phone c arrier string the carrier related to the phone number c ountrycode string the country code associated with the phone number linkclicked boolean boolean informing of whether the instant link was clicked before it expired (5 minute limit) phonematch string indicates if, after the link was clicked and mobile network operator (mno) carrier authentication successfully performed, the link was clicked on by the intended mobile device possible results true mno successfully matched the expected phone number and the sim of the device that cliicked the link false mno authendicated the sim card but phone did not match the expected phone number indeterminate mno could not determine the sim information of the device, likely due to being on a wi fi network ipaddressmatch boolean boolean indicating if the ip address of the reqeust matches the ip address of the original link generation request sample response successful response (after the link is clicked) { "result" { "transactionid" "12225083692", "carrier" "t mobile usa", "linetype" "mobile", "countrycode" "us", "linkclicked" true, "phonematch" "indeterminate", "sessionid" "646214d929c23b4d42c1fc39", "ipaddressmatch" true, " id" "6462150e29c23b4d42352a63" } } intermediate response (till the time link is not clicked) { "result" { "message" "please wait for sometime" } } error codes 409 (usptream down) { "error" { "name" "error", "message" "upstream down", "status" 409, "reason" "error", "type" "conflict", "statuscode" 409 } } 400 (bad request) { "error" { "statuscode" 400, "message" "params sessionid should match pattern \\"^\[0 9a fa f]{24}$\\"", "status" 400, "reason" "bad request", "type" "bad request" } } \ { "error" { "statuscode" 400, "message" "params requestid should match pattern \\"^\[0 9a fa f]{24}$\\"", "status" 400, "reason" "bad request", "type" "bad request" } } \ 500 (internal server error) { "error" { "name" "error", "message" "invalid requestid or sessionid", "status" 401, "reason" "error", "type" "unauthorized", "statuscode" 500 } } 401 (authentication) { "error" { "name" "error", "message" "invalid authentication credentials", "status" 401, "reason" "authentication error", "type" "bad request", "statuscode" 401 } } error response parameters parameter description error this parameter contains the error error name the name of the error error message the error message error status status of the api error reason reason for error error type type of the error error statuscode request status code from signzy getting help please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better you can reach out to us at help\@signzy com we strive to provide prompt and reliable assistance, ensuring your queries are addressed effectively we value your feedback and are committed to making your experience smooth and enjoyable our team is dedicated to assisting you with any needs you may have thank you for choosing our services we look forward to helping you!