Get Wallet Logs API (eStamping)

introduction embark on a seamless journey of financial transparency with the revolutionary signzy system, offering clients the ability to effortlessly access their transaction logs within a specified time range, clients can delve into a wealth of transaction details, empowering them with unparalleled visibility and control over their financial activities by utilizing the "parameter type," a powerful identifier, clients can effortlessly retrieve their estamp or echallan logs, unveiling a comprehensive record of their transactions bid farewell to uncertainty and embrace a world where financial insights are readily available at your command, courtesy of signzy's intuitive and secure platform client can check their transation logs in signzy system between a certain range of time parameter type is used to identify the estamp or echallan logs to be fetched authentication api authentication is a crucial security process that ensures authorized access to an application programming interface (api) it involves validating the identity of users or systems seeking to interact with the api please use the access token shared with you by your assigned signzy's csm please set the value of the key authorization in the headers to the access token , while making an api call in this way, signzy's system will be able to authenticate you and you will be able to make a successful api call api details the details of the api can be found here sample curl pre production curl location 'https //api preproduction signzy app/api/v3/contract/estamp/walletlogs' \\ \ header 'authorization ' \\ \ header 'content type application/json' \\ \ data '{ "startdate" "10/08/2023", "enddate" "10/08/2023", "type" "echallan" }' production curl location 'https //api signzy app/api/v3/contract/estamp/walletlogs' \\ \ header 'authorization ' \\ \ header 'content type application/json' \\ \ data '{ "startdate" "10/08/2023", "enddate" "10/08/2023", "type" "echallan" }' input parameters parameters description type mandatory/optional type estamp , echallan or revenue stamp by default estamp will be used string mandatory startdate start date string mandatory enddate end date string mandatory the duration at maximum can be 31 days sample response 200 { "result" { "logfile" " logfile " } } output parameters parameters type description logfile string csv file the following terms are used in estamp csv reports column name description sno serial number timestamp date and time of transaction contractid contract id with which it was used firstpartyname name of first party secondpartyname name of the second party statecode state code for the estamp articlecode article code for the estamp denomination value of stamp in case of stamp status status of the transaction(reverted,consumed, inprogress) certificateno certificate number of the estamp which is consumed certificatedate date of estamp when it was purchased uniquedocref unique document reference number of estamp the following terms are used in echallan csv reports column name description sno serial number timestamp date and time of transaction contractid contract id with which it was used firstpartyname name of first party secondpartyname name of the second party statecode state code for the estamp articlecode article code for the estamp amount amount of echallan status status of the transaction(reverted,consumed, inprogress) subchallanno challan number of the echallan which is consumed initialbalance initial balance of the echallan finalbalance remaning balance of the echallan provider echallan provider the following terms are used in revenue stamp csv reports column name description sno serial number timestamp date and time of transaction contractid contract id with which it was used lotno lot number allocated to the revenue stamp uniquerefno unique refernce number for the revenue stamp status status of the transaction(reverted,consumed, inprogress) initialbalance initial balance of the revenue stamp finalbalance remaning balance of the revenue stamp sample error 400 { "name" "error", "message" "", "reason" "validation error", "type" "bad request", "statuscode" 400 } 401 { "message" "invalid authentication credentials" } 404 { "name" "error", "message" "", "reason" "not found", "type" "not found", "statuscode" 404 } 500 { "error" { "name" "error", "message" "internal server error", "reason" "internal server error", "type" "internal server error", "statuscode" 500 } } error parameter parameter type description name string in case of errors, it will have the value "error" it represents an error message string message for the error reason string reasons for the error type string type of error statuscode string status code of the error error codes error code error message explanation 400 bad request input parameter has a missing required parameter or invalid inputs 401 authorization failed authorization token is invalid 404 not found not found 500 internal server error internal error at signzy, please reach out to help\@signzy com