Silent Network Authentication

introduction signzy's silent network authentication apis provides a secure, frictionless mobile verification mechanism using network based identity it enables fintechs and digital platforms to verify a user’s mobile number ownership without otps or explicit user input, by leveraging carrier header enrichment common use cases onboarding flows for users step up verification before transactions risk screening and sim change detection kyc and compliance pre checks how silent network authentication works start the session your backend calls the createauthsession api with the user’s mobile number and (optionally) mobile ip, a redirect and callback url in response, signzy returns a unique mobile verification link (mobileredirecturl) open the verification link you show this link to your user in mobile browser when the user opens it on their mobile network (not wi fi) , the mobile carrier securely confirms the device and number in the background automatic verification the network sends back a verification signal silently and the user doesn’t have to enter any code or number within a few seconds, the verification is complete get the result if you provided a callbackurl, signzy automatically sends the result (verified or not) to your server if not, you can call the getidentity api using the requestid from step 1 to fetch the verification status anytime redirect or end session after the process, the user is either redirected to your specified page (for example, back to your onboarding flow), or shown a short completion message if no redirect url was provided supported carrier networks for silent auth t mobile verizon sprint at\&t sample curl curl location 'https //api signzy us/api/v3/silent auth/createauthsession' \\ \ header 'content type application/json' \\ \ header 'authorization xxxxxx' \\ \ data '{ "mobileip" "", "mdnhint" "1xxxxx", "redirecturl" "", "callbackurl" "", "showpage" "true", "timer" "1000", "showverifscreen" "true", "options" { "mdnverify" "true" } } 'curl location 'https //api preproduction signzy us/api/v3/silent auth/createauthsession' \\ \ header 'content type application/json' \\ \ header 'authorization xxxxxx' \\ \ data '{ "mobileip" "", "mdnhint" "1xxxxx", "redirecturl" "", "callbackurl" "", "showpage" "true", "timer" "1000", "showverifscreen" "true", "options" { "mdnverify" "true" } } ' request body parameters key type mandatory description mobileip string optional the ip address of the mobile device initiating the request must be a valid ipv4 or ipv6 address empty string allowed mdnhint string required the mobile number (mdn) used for authentication must match pattern for us numbers starts with 1 followed by 10 digits (e g , 1xxxxxxxxxx) redirecturl string optional the url to which the user will be redirected after authentication must be a valid url empty string allowed callbackurl string optional the webhook endpoint to receive the authentication result must be a valid url empty string allowed showpage string ("true" / "false") optional key to dictate the behaviour of warning page if true, user will see a warning page with instruction to turn off the wifi default is "false" timer string optional duration in milliseconds for which if the warning page if marked true must be shown must be in string between "1000"to "60000" showverifscreen string ("true" / "false") optional whether to show the verification result screen after completion in case false, the user will see a general message default is "false" options object required object containing additional configuration options options mdnverify string ("true") required indicates if mdn verification should be performed must be "true" sample response response { "result" { "datetime" "2025 10 06t07 32 41 868z", "requestid" "68e3709a20edce80fxxxxxxx", "status" "success", "sessionid" "608e4c3a 1005 4eff af56 xxxxxxx", "mobileredirecturl" "https //api signzy us/api/v3/silent auth/identifydevice?sessionid=608e4c3a 1005 4eff af56 xxxxxxx" }, "reason" "request successful", "code" "s001" } response body parameters key type description result object contains the response details for the created silent auth session result datetime string the timestamp when the request was processed, in iso 8601 utc format example 2025 10 06t07 32 41 868z result requestid string unique identifier assigned to the api request for tracking this will be used in the second api call example 68e3709a20edce80f911xxxx result status string indicates the status of the silent auth session creation result sessionid string unique identifier for the created silent auth session used for subsequent verification or device identification calls example 608e4c3a 1005 4eff af56 xxxxxx result mobileredirecturl string url to which the mobile device should be redirected for device identification example https //api signzy us/api/v3/silent auth/identifydevice?sessionid=608e4c3a 1005 4eff af56 xxxx reason string descriptive message explaining the overall response status example request successful code string response code representing the outcome of the api request example s001 sample error e601 internal server error { "result" {}, "reason" "internal server error", "status" "failure", "code" "e601" } e001 invalid regex ### invalid `mobileip` { "result" {}, "reason" "mobileip must be a valid ip address", "code" "e001" } \### missing `mdnhint` { "result" {}, "reason" "mdnhint is required", "code" "e001" } \### bad `mdnhint` format { "result" {}, "reason" "mdnhint must be a valid us mobile number (1 + 10 digits)", "code" "e001" } \### invalid `redirecturl` { "result" {}, "reason" "redirecturl must be a valid uri", "code" "e001" } \### invalid `callbackurl` { "result" {}, "reason" "callbackurl must be a valid uri", "code" "e001" } \### invalid `showpage` { "result" {}, "reason" "showpage must be either \\"true\\" or \\"false\\"", "code" "e001" } \### invalid `showverifscreen` { "result" {}, "reason" "showverifscreen must be either \\"true\\" or \\"false\\"", "code" "e001" } \### `timer` not numeric { "result" {}, "reason" "timer must be a valid number in milliseconds", "code" "e001" } \### `timer` < 1000 { "result" {}, "reason" "timer must be at least 1000ms (1 second)", "code" "e001" } \### `timer` > 60000 { "result" {}, "reason" "timer cannot exceed 60000ms (1 minute)", "code" "e001" } \### missing `options` { "result" {}, "reason" "options is required", "code" "e001" } \### missing `options mdnverify` { "result" {}, "reason" "mdnverify is required", "code" "e001" } \### `options mdnverify` not `"true"` { "result" {}, "reason" "mdnverify must be \\"true\\" only", "code" "e001" } e401 upstream failure { "result" {}, "reason" "upstream error", "code" "e401" } error response parameters parameter description result empty result object reason reason for error c ode error code from signzy error codes http status code error code description 400 e001 bad request 401 e101 unauthorized access 403 e201 forbidden 404 e301 not found 409 e401 upstream error 429 e501 rate limit exceeded 500 e601 internal server error 503 e701 service unavailable 504 e801 timeout success codes http status code success code description 200 s001 request successful get identity api the get identity api retrieves verified mobile network information after a successful silent auth session this api uses the requestid obtained from the createauthsession api to fetch verification results api details need to pass the following information providing requestid is mandatory requestid (required) sample curl curl location 'https //api preproduction signzy us/api/v3/silent auth/getidentity' \\ \ header 'content type application/json' \\ \ header 'authorization \<auth token>' \\ \ data '{ "requestid" "\<requestid>" }'curl location 'https //api signzy us/api/v3/silent auth/getidentity' \\ \ header 'content type application/json' \\ \ header 'authorization \<auth token>' \\ \ data '{ "requestid" "\<requestid>" }' request body parameters the api expects the following input in the request payload { "requestid" "\<request id> (obtained from the first api)", } parameter data type required description requestid string yes required unique request id generated for the input provided in async api sample response success s001 { "result" { "requestid" "68e372e820edce80f911xxxx", "sessionid" "session tc001 1759736552703 xxxxx", "status" "success", "mdnverified" "true" }, "reason" "request successful", "code" "s001" } success s003 { "result" {}, "reason" "data not found", "code" "s003" } response body parameters key type description result object contains verification results for the given requestid result requestid string the unique identifier of the request, matching the input requestid result sessionid string the unique session identifier associated with the silent auth verification process result status string indicates the overall result of the verification possible values success , error result mdnverified string ( "true" / "false" ) indicates whether the mdn (mobile directory number) verification was successful reason string a human readable description of the api response outcome example "request successful" code string api status code indicating success or failure example "s001" for successful responses sample error e301 not found { "result" {}, "reason" "session not found for requestid", "code" "e301" } error response parameters parameter description result empty result object reason reason for error c ode error code from signzy error codes http status code error code description 400 e001 bad request 401 e101 unauthorized access 403 e201 forbidden 404 e301 not found 409 e401 upstream error 429 e501 rate limit exceeded 500 e601 internal server error 503 e701 service unavailable 504 e801 timeout success codes http status code success code description 200 s001 request successful 200 s003 data not found 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!