-
Recently active
While using the Box .NET(Gen) SDK I noticed that the TemplateSigner class is missing the label field. However when calling the Box API via curl to get sign templates the label field is a part of the signer objects in the signers array on sign templates. I assume it is supposed to be accessible as this forum post describes the signer object as having the label field. https://community.box.com/topic/show?tid=477&fid=9 Unfortunately, the label field is missing on the Signers object on this page Box Sign template - API Reference - Box Developer Documentation of the Box Developer Documentation. Upon closer inspection it also appears to be missing on all of the SDKs TemplateSigner classes.
Dear Box Support Team,I hope this message finds you well. We are currently in the process of integrating Box API functionalities into our application. While we have successfully accessed sign requests through the Box API, we have encountered specific requirement that we are seeking clarification on:Checking if a User Has Signed a Document: We need functionality in the Box API that allows us to determine whether a specific user has already signed a document. Unfortunately, We didn't find this functionality in the current Box API for sign requests. Are there alternative methods we could utilize?Thanks.
The documentation at https://developer.box.com/guides/embed/box-embed/ briefly mentions that postMessage() is used to retrieve status, but I can’t seem to make it work. I’ve setup an event listener for the message event, but it does not fire. I’ve also tried calling postMessage on the iframes contentWindow property, but to no effect.
In this YouTube tutorial by Box , at minute 1:58, they demonstrate a popup modal with a Box Sign embedded. It seems that this isn’t an iframeable_embed_url because the Cloud Game widget doesn’t pop up. When I use the iframeable_embed_url in my own modal, upon a user signing, instead of the user being shown a screen that says “Finished. Thank you for completing the request” like is shown upon sign completion in the YouTube tutorial, the Cloud Game widget pops up again. When the user completes this game (for a second time now), they then see a blank screen. This makes for a poor user experience because the user has no indication of whether or not their sign was successful. Is it possible for me to embed the embed_url into my modal instead (seemingly like what is done in the tutorial)? It seems like if I do so, the user won’t have to deal with the Cloud Game and weird sign completion experience. If not, what must happen for the user to be shown the “Finished. Thank you for completing the
Api Path : https://{{api.box.com}}/2.0/sign_requests Request Body: { "is_document_preparation_needed": true, "parent_folder": { "id": "242033790140", "type": "folder" }, "name": "new file", "days_valid": 2, "source_files": [ { "id": "1402075677437", "type": "file" } ], "signature_color": "blue", "signers": [ { "email": "abc@gmail.com", "role": "final_copy_reader" } ] } Response : { "type": "error", "code": "bad_request", "status": 400, "message": "Bad request", "help_url": "https://developer.box.com/guides/api-calls/permissions-and-errors/common-errors/", "request_id": "0161f8a960ede1346f50bfdc34b75156f", "context_info": { "errors": [ { "name": "source_files", "message": "Enter a valid file.", "reason": "invalid_parameter" } ] } }
Dear Forum, For several months, I’ve been using Box drive for sync’ign with local folders - with no issue. Since last week, I can still login to the online box, but get an SSL error when trying to connect to the Box drive. I checked with my IT team (no change on that side), tried resetting password, no effect. I uninstalled/re-installed, but get to the same point. Coudl it be comign from a recent updates? Any ideas on how to address it? Thanks! 2023-12-16 19:17:49.975 14628 INFO CompleteAuthenticati network_layer Got a SSLError so calling refresh_proxy_settings: BoxHTTPSConnectionPool(host=‘api.box.com’, port=443): Max retries exceeded with url: /oauth2/token (Caused by SSLError(SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate signature failure (_ssl.c:997)’)))
Hi, I am currently using the Sign Request API to prefill a pre-created sign template with some data for a signer. Most of the time, my fields prefill completely as expected. (I’m passing them in prefill_tags => {document_tag_id: "tag_name", "text_value": "value" } format, and that seems to be working.) However, every once in a while (maybe like one in every 4 sign requests?) my fields don’t populate correctly and are blank for the signer. I haven’t been able to identify any consistent similarities between these cases, and the success/failure cases have been with the exact same code and request pattern. Any thoughts on what might be going on here?
I am using the create sign request API with the following body to create a sign request: { "external_id": "10000", "parent_folder": { "id": "0", "type": "folder" }, "signers": [ { "role": "signer", "email": "ben.jessup@oasisdigital.com" }, { "role": "approver", "email": "benjamin.jessup@valiantys.com" } ], "source_files": [ { "id": "1056087946155", "type": "file" } ] } After signing and approving the request it goes into a “finalizing” state (shown as “In Progress” in the UI), then eventually goes into a “error_finalizing” status. Initially I encountered this in a Atlassian Connect Express application, but I saw the same behavior after using Postman to create the sign request. Any thoughts on what could be causing this error? Is there any way to see more detail on the error?
Introducing: Template APIs for Box Sign! Finally we can use the ‘/sign_request’ end point to create a signature request. Let’s start with the ‘template_id’: 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.
I am using the Box Sign API to create sign requests based on a sign template named “SimpleAckTemplate.pdf” for example. By default, both the sign document and the signing log would be named “SimpleAckTemplate (1).pdf” and “SimpleAckTemplate (1) Signing Log.pdf” respectively. I would like to change the file names using the “name” parameter in the API changing it to “SimpleAckTemplate_nnn” where nnn is our internal number. It seems to work partially as only the log file was changed. The sign file name was still defaulting to “SimpleAckTemplate (2).pdf”. I didn’t see another parameter in API that I can use. When making the sign request on Box Sign Web UI, both file names for log and sign would change per value specified on the “File Name” field. I don’t know what I am missing in the API. Thanks
Update: The Good, the Bad, and the Ugly… I made a fresh test template for this stuff and setting the Dropdown text via the API worked, so I’m happy about that. I ran into something which I don’t remember being the case before, which was that Sender fields did not even appear to the Signer/Recipient. –I would assume that they’d just be non-modifiable but visible. –Is there some setting I forgot about? Regarding the Radio buttons I tried on Brave browser where they were better performing than Firefox, but not perfect I still see this as a Radio Button conceptual problem, as they aren’t fully taken as a group As the issue seems to be the Arrow indicator can get out of sync with the button-click Meaning that if an entire Radio Button group was considered one item, there’d be no issue Regarding the Text field “Ownership Change” What starts out as a Sender field seems to turn into a Signer field upon text change via API Even if I’m not doing something right, this seems like a bad behavi
We are excited to introduce a new embedded signing experience, enabling developers to leverage the power of Box Sign within custom applications! Developers and users can now embed the Box Sign signing experience into their own custom applications without the need to navigate to Box Sign and back into their custom application to complete the signature process. To integrate Box Sign experience within your own website, you need the iframeable_embed_url parameter that is specifically designed to allow signing documents within the HTML iframe tag. A sample iframable_embed_url looks as follows: https://app.box.com/embed/sign/document/f14d7098-a331-494b-808b-79bc7f3992a3/f14d7098-a331-494b-808b-79bc7f3992a4 To get the iframeable_embed_url pass the embed_url_external_user_id parameter for each signer when calling the create sign request endpoint. The returned response will contain a unique iframeable_embed_url for that signer. To embed Sign features and make them available to the users, use
During my sandbox app testing, I was shocked that, as a Signer, I could DELETE text fields that are for the Sender / (tagged as 0) And then I could set the text to anything I wanted. Is there a way to FORCE READ-ONLY on Sender text fields (which should be the default anyway)?? Note: I was switching to Text Fields from Dropdowns, as Dropdowns are not properly supported via the API yet. This is very frustrating. Also: I suggest the box devs try using Radio Buttons as a Signer to see how buggy they are. (Try selecting one, then selecting another–You will have to fight with it quite a bit–Unacceptable UX.) Thanks.
Hi all, I create an application and I use private / public key for authenticate. I use .net sdk to upload a file, create a sign request to 1 email and everythinks works fine. After that I recieved the email to sign the document and I can sign it, but after signing the document the sign request is never validated. I don’t have any other emails about errors. Is there a way to have the sign request status ? I try to do the same process manually and it’s work. Did I miss something ?
We are excited to introduce new extensibility features that enable developers to leverage the power of Box Sign within custom applications! Developers can now leverage Box Sign reusable template capabilities within custom applications with reusable template APIs. With template APIs , developers can enable the following capabilities for senders when integrating Box Sign with custom applications: Provide a list of all their Box Sign reusable templates Obtain template details via associated template IDs Initiate signature requests using specific templates The first step to leveraging this capability is to create the reusable template within the Box Sign native web application within Box. From there, senders can send a sign request using the template they just created, and pre-populate the full name placeholders. First, users need a ‘template_id’ to identify which template they will be using. We can list all the available templates using the ‘/sign_templates’ end point: curl --location '
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
