Delete Template API

introduction welcome to the delete template api documentation this comprehensive guide will walk you through the seamless process of utilizing our powerful api endpoint designed to remove templates from our system effortlessly by integrating this feature into your application, you can efficiently manage your template repository, ensuring a streamlined and organized workflow with just a simple input of the template id, you can swiftly delete templates, enhancing the flexibility and responsiveness of your platform join us as we delve into the details of how to leverage the delete template api to effectively maintain your template ecosystem and keep your system clutter free let's embark on this journey to harness the full potential of template management within your application 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 request delete 'https //api preproduction signzy app/api/v3/template/delete/\ templateid' \\ \ header 'authorization ' \\ \ header 'content type application/json' \\ \ data '{ }' production curl location request delete 'https //api signzy app/api/v3/template/delete/\ templateid' \\ \ header 'authorization ' \\ \ header 'content type application/json' \\ \ data '{ }' sample response 200 { 	"status" "success/failure", 	"statusdesp" "description", } output parameters key description type status indicates the status of the operation string statusdesp description of the status string sample errors 400 { "name" "error", "message" "invalid url extension", "reason" "validation error", "type" "bad request", "statuscode" 400 } 401 { "message" "invalid authentication credentials" } 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 500 internal server error internal error at signzy, please write to us at help\@signzy com