Box Sign API - Template ID
I have just been informed that template_id is a new POST body param, and while you can use template_id and it will utilize a template in the box sign request creation, it does not seem to be populating anything.
Previously, prefill_tags was utilized to populate flat files with hard coded markup placed inside to populate data. Utilizing templates from within box sign platform places an "inputs" array inside the signer array for each signer, with similar data as prefill_tags used.
I tried using both prefill_tags and putting inputs into signers array, neither seems to be working. I know this was just recently released, does anyone have any information on how to utilize it? Doesn't appear it's been documented yet on the official api documentation, or implemented into any SDKs.
I'm not sure if the template_id has in fact been released yet, I'll investigate, but I don't think so.
To get you started and even before looking into the prefill_tags, let me point you to this support document describing how to create "templates" than can be used with the sign API.
You can also find a collection of example documents illustrating how to use the "tags".
We've also create a sample app that contains a sign from a template use case. You can find the article here, and the sample app on this GitHub repo.
Let me know if this helps with your use case.
Box Sign Templates API has been officially released.
You now have a /sign_templates end point to list and get the templates, and also the template_id parameter on the create sign request.
We tired new template feature in document sign in API but stumble with mysterious 404 error. When calling:
we get list of all sign in templates as expected. Yet call to
where <template_id> is any of ids returned in previous call yields 404. The same behavior we experience when trying to call sign_requests endpoint with given <template_id>. We checked scopes and template permissions for the our App but we don't know what to check next :-(
Please sign in to leave a comment.