One Touch Sign (OTS)
Template Engine
Get Template By Template ID API
8 min
introduction unlock instant access to template specifics with our get template by template id api retrieve in depth template details effortlessly by providing the unique template id whether it's template names, files, or any other crucial information you seek, our api delivers precisely what you need say goodbye to guesswork and hello to pinpoint template retrieval simplify your workflow with the get template by template id api – your gateway to seamless template management start optimizing your template retrieval process today! 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 get 'https //api preproduction signzy app/api/v3/template/get/\ templateid' \\ \ header 'authorization ' \\ \ header 'content type application/json' \\ \ data '{ }' production curl location request get 'https //api signzy app/api/v3/template/get/\ templateid' \\ \ header 'authorization ' \\ \ header 'content type application/json' \\ \ data '{ }' sample response 200 { "status" "success", "statusdesp" "search successfully", "templatedetails" \[{ "templatename" "name of template", "templatetype" "docx, html, editablepdf", 	"templatedata" "url or base64", "templaterequiredvariables" "json data keys to be filled in template in desired format", "templateid" "" }] } output parameters true false 164false 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 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 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 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 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 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 false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type