This functionality is currently broken. If a template_id is added to a sign_request, the request fails with a 404. Without the template_id, the sign request works as expected. The same 404 behavior is seen with the sign_templates/:template_id request to get a specific template by ID.
404 Error When Adding Sign Template
Best answer by xyz
Thanks for troubleshooting this issue with me today, @rbarbosa .
The CCG app (client credentials grant) app that is intended to be used for server-side automations has a service account user that’s supposed to be used with the API rather than my managed user account. If I create a sign template with my managed user account, then the service account user can see the details of that template from the GET https://api.box.com/2.0/sign_templates endpoint but is unable to access those same template details one at a time with the GET https://api.box.com/2.0/sign_templates/:template_id or use that template in POST https://api.box.com/2.0/sign_requests calls.
However, if I instead create the template with the service account user via the Box web console (using the “Log in to user’s account” feature from the Admin Console | Content | right-click user menu), then the template is usable by the service account user that’s invoking the API.
The issue seems to be permissions related to sharing content (sign templates) from a managed user to a service account user and the API behaving in away that makes them available for list access but not for individual access or use in an actual sign request.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
