Box Sign API

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 enabling embed_url_external_user_id suppresses the email notification?-Is there any way to enable both embedded signing and email notification simul

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 = GetTokenAuthorisation();BoxClient client = GetBoxClient(auth);// Upload Filestring fullPath = @"C:\Users\srodney_dev\AppData\Local\BoxTest\TesstingBoxUpload.docx";/

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,          "page_index": 0,          "width": 150,          "height": 50        }      ]    }  ],  "source_files": [    {      "id": "1714359484288",      "t

I put Box Sign projects on hold for a year in hopes box.com would fix various web UI bugs insigning documents.Sadly, I still see an unacceptable overstrike and now even multiple font sizes on that overstrike, etc. But now that I’ve come back, I find that I can no longer get CCG to work with the User ID set inthe app.  ( CCGAuth() in Python SDK. )  The initial authorization works when using Enterprise IDBUT that is not what I want because when using the Enterprise ID, it never could access mytemplates--They were only accessible when using the user id.  (the User ID in the app config.)( It was previously able to access them when using the “user” argument to CCGAuth(). )I changed nothing.  It stopped working.  Yes it was still authorized then reauthorized for good measure.Is this a bug or a feature?  And is there a way to get the old behavior?  Other than this:Sadly I had to switch back to regular OAuth2 using the annoying 1 hour temporary dev tokenswhere it still will access the template

I have a template which works just fine with prefill_tags and defined signature placement, etc. The moment I try to add other files i’ve previously uploaded (and captured id’s of) via source_files and additional_documents in the payload, the template becomes null and the signature request will only include those additional documents. That is to say, I cannot find a way to use both a template and add additional files to a signature request. I am using jwt authentication in python. 

The ID used in the Get Sign Requests by ID endpoint is a 36-character alphanumeric string; the same type as returned from “id” in the response from Create Box Sign Request. Where can I find this id in the UI?The only IDs I can find in the UI are an 8-character alphanumeric “Request ID” when viewing a Sign Request > See Details, or a 13-digit numeric ID on the in the sign request’s document URL. Neither of these work when trying to use the Get Sign Requests by ID endpoint. Alternatively, can I retrieve this elusive ID via an endpoint, using either of the two IDs I can see in the UI?

Hello,I am using the create sign request API with the following body to create a sign request:{"external_id": "id","parent_folder": { "id": "1234", "type": "folder" },"signers": [     { "role": "signer", "email": "email@email.com" },     { "role": "signer", "email": "email2@email.com" },    { "role": "final_copy_reader", "email": "email2@email.com" }],"source_files": [ { "id": "12233", "type": "file" }, { "id": "54321", "type": "file" } ],“is_document_preparation_needed”: true} The sign request successfully achieves the “Created” state. However, the prepare SR URL gives a 404 to the actual user, who is supposed to configure the SR before sending it out. I suspect this is happening because the service account is the actual owner of the SR. My question is, how can I create an SR via API but assign an actual person as its owner? Thank you.

Hi Development Team,As part of our project we need to upload documents to one of the folder in Box CLI. We have folder ready in Box CLI and commands to be given in command prompt. Here we wanted to automate the commands which we are giving in Command prompt of our system using bat file. But it is not accepting the Client Id and Client Secret. Could you please help us to automate this process.Thanks and RegardsSravya Pericherla.

Hi there,I am using the Embedded Signing Experience to embed signable documents into a web page using an iframable_embed_url. I use the Create Box Sign request API to retreive the embeddable URL. The embed is working fine, including te signing functionality, but my document contains one user-fillable field whose value I need to retrieve after signing. In the Sign Template editor, I've given the form field an External Identifier to make the input easer to find, but I can't find a way to fetch what the user put into that field after signing.I hoped that the "Sign Completed" webhook would include all the document's input data, but it does not. https://developer.box.com/reference/resources/webhook-invocation/Then I took the Sign Request ID (additional_info.sign_request_id) from the webhook response, and passed it to the "Get Box Sign request by ID" API. Despite the documentation showing Signers and Inputs on the response, that data is not present in my response. https://developer.box.com/r

Hi there,I'm using the Embedded Signing Experience to show my users a document they need to sign. I call the Create Box Sign request API to retreive the embeddable URL, and immediately embed the iframable_embed_url onto my page. At this point, the cloud matching captcha displays. If I wait 5-7 seconds and then complete the captcha, the signable document displays. But if I complete the captcha immediately, the page shows "Invalid Link: This request link is invalid."It seems like the template file gets copied to make a signable instance at the same time the endpoint returns, but the document copy is not finished yet, and if the users proceeds too fast, they attempt to access an instance that isn't done being created yet.

I would like to download the signed document after all the signers have completed the signatures. In trying to do so, I am trying to call download API by providing the file id:https://{{api.box.com}}/2.0/files/{file_id}/contentAfter checking the status of sign request, which is “signed”, I am trying to download the document. However, it is still resulting in the document which is not signed/without signatures.Can you please help me understand, how to get the signed document through API.Thanks in advance.RegardsVenky