Remind Signer API

introduction in today's fast paced digital landscape, efficient communication and streamlined processes are vital for businesses to thrive the remind signer api emerges as a powerful tool designed to enhance the contract signing experience by facilitating timely reminders to signers with the ability to seamlessly integrate into existing systems, this api offers a straightforward solution for organizations seeking to optimize their contract management workflows the remind signer api operates on a simple premise to prompt signers to execute contracts promptly and conveniently by leveraging unique identifiers such as signer ids, this api initiates personalized reminders through various channels including email, sms, and whatsapp through targeted communication, signers are gently nudged towards fulfilling their signing obligations, thereby expediting the overall contract execution process this introduction serves as a gateway to understanding the capabilities and functionalities of the remind signer api in the subsequent sections, we delve deeper into its features, implementation strategies, and the transformative impact it can have on modern business operations join us as we explore how the remind signer api revolutionizes contract management and fosters enhanced efficiency and reliability in the digital era 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/remindsigner' \\ \ header 'authorization ' \\ \ header 'content type application/json' \\ \ data '{ "signerid" " " }' production curl location 'https //api signzy app/api/v3/contract/remindsigner' \\ \ header 'authorization ' \\ \ header 'content type application/json' \\ \ data '{ "signerid" " " }' input parameters key description type mandatory/optional signerid id of the signer for which the signature type needs to be changed string mandatory sample response 200 { "issuccess" true } output parameters field name description type issuccess the status for the updation of the remind signer api string sample errors 400 { "name" "error", "message" "reminder can not be send ", "reason" "bad request", "type" "not found", "statuscode" 404 } 400 { "name" "error", "message" "signerid is required", "reason" "validation error", "type" "bad request", "statuscode" 400 } 400 { "name" "error", "message" "signer already signed cannot send reminders", "reason" "bad request", "type" "bad request", "statuscode" 400 } 400 { "name" "error", "message" "signer already signed", "reason" "bad request", "type" "bad request", "statuscode" 400 } 401 { "message" "invalid authentication credentials" } 404 { "name" "error", "message" "signer not found", "reason" "bad request", "type" "not found", "statuscode" 404 } 500 { "error" { "name" "error", "message" "internal server error", "reason" "internal server error", "type" "internal server error", "statuscode" 500 } } error parameters 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 signer id is not found in the system 500 internal server error internal error at signzy, please reach out to help\@signzy com