Box Sign API

Hello,We are currently using Box Sign to send documents for signature and have encountered two issues.Firstly, we are receiving blank signed documents mixed in with our fully executed documents. Is there a way to prevent this, or a workaround to eliminate blank documents from being included?Secondly, regarding the signing logs: is there a way to automatically move them to a separate folder instead of keeping them in the same folder as the completed documents? I attempted to set up a Relay workflow, but it is not moving the signing logs out of the completed documents folder.Is there a better approach to achieve this, or could I be missing something in my Relay setup?Thank you for your time, and I look forward to your guidance.Best Regrads,Stephanie

I would like to request for signature scopes. I have the starter plan, but do not see it in my app configuration.  One of the docs mentioned that need to request.  Kinda annoying honestly. 

Hello,We have created a Box Sign document template and would like to send it to multiple existing users for signature in an automated way. I am not an admin and have been trying to achieve this using automation tools like Zapier and n8n.Currently, I have a workflow that reads rows from a Google Sheet (containing user email and template ID) and attempts to send a Box Sign request when a new row is added. However, I am encountering permission-related errors (insufficient scope / 403) when calling the Box Sign API.From my understanding, this might be due to missing Box Sign API permissions (e.g., sign_requests.write) or lack of access to Box Sign for my account.Could you please confirm: Do I need admin approval or additional permissions to use the Box Sign API? Is it possible to automate sending Box Sign requests without admin involvement? Are there recommended approaches or tools for this use c

I’m trying to send a sign request using a template and it doesn’t seem to be working - the recipient is not getting the email invite.I also tried sending an invite via api with the new Box Developer Playground (with an embed link) and even though the response is 200 OK and the sign request status is “created” the returned embed_url doesn’t work properly - when I use the link the sign page shows a message “Invalid Link”.It worked fine earlier today, is anyone else experiencing the same issue?

I was trying to login to box.com with existing organizational email id, since there is transition in email id inadvertently, I deleted the account from which I already logged in. The new mail id should have been the primary one which i am not able to login as i get the pop-up message as “Account already exists for that mail id” (which was inadvertently deleted - [removed by moderator] ). As of now I already logged in to box with my secondary organizational email id which may stop working anytime. i need to switch my email id for the Box.com login. Could someone please help me out on this scenario.

Hello, whenever I send a document for signature and I add in an attachment, the final signed version does not include in the attachment. EG I have file 1 and file 2. File 1 contains the signature requests but file 2 does not. After all parties sign the document, the finalized signed document only contains file 1 but not file 2. Is there a way to have Box export both the finalized signed file 1 and file 2 combined into one PDF automatically?

I need any Box Sign Certification – EU eIDAS Regulation Knowledge Paper, or any other official documentation verifying Box Sign’s compliance with relevant legal standards. I cant find any supporting document to the validity of box sign. as Box is not a Qualified Trust Service Provider (QTSP) under eIDAS, im tryong to understand what is the name of the QTSP (if any) that issues the qualified certificates when using Box Sign in Europe? 

I don’t understand how we are supposed to handle signing log files. If we keep them as they are now, every revision we release through the Box sign process will generate a new signing log. We’ll end up with multiple signing logs, for each file. On top of that, if we search for a file, these signing logs appear in the results, unnecessarily confusing users. I understand the advantage of having them available, but it doesn’t make sense to treat them as a normal file.What is everyone else doing?

 We’re using the Box Sign REST API to send documents for signature. The document template already includes predefined signer blocks (created using FormStack).While sending the document, we dynamically set the signing order at runtime. For example, if we choose to have signer ABC sign first and signer XYZ sign second, the document should direct ABC to their specific signing block first, and then XYZ to theirs.The issue is that we need a way to uniquely associate each signer with their corresponding predefined signing block, so that Box Sign correctly routes each signer to their designated area, based on the runtime-defined signing order.Can you please advise how to handle this scenario?

I’m using the Box Sign API to send a signature request using the POST /sign-requests endpoint:https://developer.box.com/reference/post-sign-requests/I’ve included HTML-formatted text in the email_message field so the email content appears styled (e.g., bold text, line breaks, etc.).The email is received correctly — the formatting in the email appears to be fine. However, in the signature request view, the email text is displayed with raw HTML tags instead of being rendered as formatted text.Is there a way to make the HTML render properly in the signature request, or does the API only support plain text for this field?Thanks in advance for your help!

I'm having issues with Box Sign.  I have to agree to sign each time I sign, even if one right after the other.  I have to go back to the main search page and reset the filters (pending my action).  Is there a way to open each signature in a new tab?  Or better yet, set the default to open the next envelope?  It is really depressing when you have to sign 50 envelopes.

I am currently able to send documents for electronic signature to members of my organization, whose names and email addresses auto-populate when adding them. However, I cannot find a way to add contact names and email addresses for persons outside my organization so that they, too, auto-populate when attempting to add them. Is there a way to import and/or create a contacts list for signatories outside of my company? 

📌 Use Case:-For existing sign requests, we need to retrieve the embedded signing URL.-For new sign requests, we need both:-The embedded signing experience (embed_url_external_user_id)-The email notification sent to the signer❗Issue:When we include the embed_url_external_user_id parameter in the request payload (to generate the embedded signing link), the email notification to the signer is not sent.-No errors are returned in the API response-The sign request is created successfully-The embedded URL is generated and works-But no email is triggered to the signer✅ Expected Behavior:-When creating a new sign request and providing embed_url_external_user_id, we expect:-The signer to receive the standard email notification-The embedded URL to be available as an alternative signing option🔍 Request for Clarification:-Is it expected behavior that en

I have recently set up a free Box account. I’m having issue with Requesting a Signature. The request signature box is grayed out. Why? Based on the data for the free account, I should have the ability to send 5 documents for signature per month. I have not routed any documents for signatures in July. Please advise. Upon logging in with my EDGE Browser, this is the error message that I receive. I’ve current using another Box account with the same browser, so the browser is not the problem. Can you please take a look on the back end and see if something is not set correctly.  Thanks! 

Hello,according to the API-doc there’s no possibility to create templates using the API. Are there any plans to enable this in the future.I imagine posting a structured pdf-file with tags through an API-call…Thank you very much in advance for you feedback!Jan

When you open the first file in Box, the file_id is set correctly to the ID of the first file opened, but if you then open a second file, the file_id may remain the ID of the first file. If you then reopen the second file, the file_id will be correctly updated to the ID of the second file, but please check to see if this is an issue on the BOX side.

Hello,An Excel document layout changes from portrait to landscape and becomes 2 pages when uploaded to box sign. is there any way to keep the original layout of the document? 

I clicked the check box for signature groups but it gives me the error when trying to send to be signed.  "User is missing permissions: sign_recipient_groups" Also is there a limit to the number of requests a month? Free tier  Also can free tier use the API to sign stuff? 

We use a dynamic stamp on invoices for coding, with boxes set aside for approvers to initial. When I send such a document out to 2 signers, the signature image of the first signer appears underneath the dynamic stamp, while the image of the second/final signer appears on top of the stamp (as desired). Short of flattening the documents before send, is there a way to ensure all of the signatures/initials display above the stamp in the final PDF? Thanks,Phil

Hi,  We are exploring Box sign and we have documents coming externally and would like to initiate those documents from box sign but we are not sure how we can dynamically create sign template tags on it. Any references will be appreciated Thank you

Hello, I'm trying to integrate with Retool to sign some documents via API, I've already created the app and granted all necessary scopes for it.The problem is with the OAuth2 authentication, when I authenticate with Retool, it successfully generates the access token, but it didn't grant the sign scope, even when I (on purpouse) write the scopes when I request the access token.When I try the developer token it works fine.

Using .Net SDK and the C# languageHi AllIt’s First time using this forum and the .Net SDK as well.My manager has asked me to create a prototype proof of concept app to create a signed document from our laptops. The users running the app will have their own Box Accounts.When the user executes the app, it will…Upload a document to their box account. The Box Sign behaviour, [Sign Myself], will activate and the user will fill out their signature. The Signed Doc and Log is created. The Signed Doc and Log is downloaded to the users laptopThe issue is that in order to get Box Sign to activate I Create a Sign Request which requires a Signer, even though the user is whom I want to sign the document and the behaviour is not the same as how it acts in  [Sign Myself].What am I missing?Very Rough code below… BoxDeveloperTokenAuth auth = GetTokenA

Hi community - we recently implemented Box GxP for Box Sign and we are used to having DocuSign send us the signing log as an appendix to the signed document itself.  With Box Sign, the document is separated from the signing log though you can download the latter from clicking on the three dots inside the Box Sign details screen for the document.  To that end, I want to know if there is a way to download the Box Sign log as an API call or somehow magic it so that both documents can be downloaded simultaneously.  I don’t necessarily need them joined like DocuSign would do but I definitely need to be able to pull down that Box Signing log with each document.  If it exists in the details screen, my assumption is there must be a way to retrieve it via the API.  Any and all suggestions are welcome!! Nate

I encountered a 500 error while using Postman to call the Box Sign API to create a sign request:Endpoint:https://api.box.com/2.0/sign_requestsDetails:The same developer token successfully works for file uploads. The application is approved and authorized.Could you help identify the possible reasons for the issue? { "type": "error", "code": "internal_server_error", "status": 500, "message": "Internal Server Error", "help_url": "https://developer.box.com/guides/api-calls/permissions-and-errors/common-errors/", "request_id": "0301ec73ba5420dac2e91dc81cc5f2845"}

I am trying to create a Box sign request and want to highlight the signature box in the document where the user needs to add their signature. In the Box Sign portal, there is an option to drag and drop the signature and other fields, which places the signature box at the desired position in the document. I want to replicate this functionality using code. However, when I tried adding the inputs attribute under signers, it didn’t work as expected.Below is my json request body.{  "email_message": "Hello! Please sign the document below",  "email_subject": "Sign Request from UserName",  "parent_folder": {    "id": "2895123232312",    "type": "folder"  },  "signers": [    {      "email": "<useremail>",      "role": "signer",     "order": 1,      "inputs": [        {          "type": "signature",          "x": 100,          "y": 150,