Delete DocSignConfig API

introduction welcome to the delete docsignconfig api documentation! this comprehensive guide will show you an efficient process to remove dsc class 2, dsc class 3 certificates, company seals, or authorized signatures uploaded for auto virtual signing from your system using our robust api whether you're a developer integrating this feature into your application or an administrator managing digital certificates, this api empowers you to effortlessly delete dsc certificates or uploaded signatures/seals files by their unique certificate id by following the instructions outlined in this documentation, you'll be able to streamline your certificate management workflow and ensure the security and integrity of your digital assets let's dive in and explore how to leverage the delete docsignconfig api to efficiently manage your certificates 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/esign/deletedocsignconfig' \\ \ header 'content type application/json' \\ \ header 'authorization ' \\ \ data '{ "certificateid" "" }' production curl location request delete 'https //api signzy app/api/v3/esign/deletedocsignconfig' \\ \ header 'content type application/json' \\ \ header 'authorization ' \\ \ data '{ "certificateid" "" }' input parameters true false 152,74,113false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type sample response 200 { "deleted" true } output parameters true falsefalse unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type sample errors 400 { "name" "error", "message" "certificateid is not allowed to be empty", "reason" "validation error", "type" "bad request", "statuscode" 400 } 401 { "message" "invalid authentication credentials" } 404 { "name" "error", "message" "certificate not found", "reason" "error", "type" "not found", "statuscode" 404 } 500 { "message" "internal server error" } error parameter false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type error codes false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type