-
Recently active
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 behavior No
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 th
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 'ht
9 likes
5 likes
3 likes
2 likes
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.
We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
