EzKRA (KRA Microservice)

Customer Login (Client Login)

6 min

introduction for using signzy apis you have to first log in to signzy system which is a simple rest api(https) call with json parameters as username and password the following section mentions the data to be input, the expected output, and the meaning of fields in json api endpoint customer login api preproduction https //backops investor onboarding preproduction signzy tech/kra handler/api/customers/login production https //backops investor onboarding signzy tech/kra handler/api/customers/login sample request curl location 'https //backops investor onboarding preproduction signzy tech/kra handler/api/customers/login' \\ \ header 'content type application/json' \\ \ header 'accept application/json' \\ \ data raw '{ "username" " username ", "password" " password\@123 " }' request field description key data type required/optional description header content type string required application/json body username string required username of the created customer password string required the corresponding password of the username is to be used for successful login sample responses a successful api request generates an http 200 response the response to a request where the output format was specified as json, is a json array with a response status to get the authentication token, look at the following response having the parameter “id” the userid is the customer id 200 { "id" "jgzqxxxxxxt2i8s", "ttl" 1209600, "created" "2023 03 02t15 21 31 457z", "userid" "5exxxxxxxxaa" } 400 bad syntax error { "error" { "statuscode" 400, "name" "syntaxerror", "message" "unexpected string in json at position 31" } } 401 { "error" { "statuscode" 401, "name" "error", "message" "login failed", "code" "login failed" } } 404 { "error" { "statuscode" 404, "name" "error", "message" "there is no method to handle post /login" } } 502 \<html> \<head> \<title>502 bad gateway\</title> \</head> \<body> \<center> \<h1>502 bad gateway\</h1> \</center> \</body> \</html> response field description key data type description id string this is your access token to be passed into other endpoints as an authorization header ttl string time to live for your token, which means for how much time this token will be valid from the time of the creation created string time and date of creation of the application userid string the id of the user 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