Skip to main content
Question

Box Sign API - individual sign URLs for signers

  • May 23, 2025
  • 6 replies
  • 47 views
C
Forum|alt.badge.img

I am using the Box Sign API with the Python SDK to generate sign requests for organizations using my products. The organizations have as few as 1 and as many as 35 users. I do not have a problem generating the sign requests from script. The trouble I run into is that when you have a lot of users, there is usually a "weak link" in the chain of signers.

For example, right now I have a sign request with 24 signers that has been in process for several weeks. We are hung up at the 20th signer. She swears that she does not see the requests in her email, including spam and promotions. I have checked and rechecked the email address. Ironically, this group of users is actually within my overarching organization (university) so we are on the same domain. I have not received any bounce notifications.

I would like to be able to obtain the URL for her sign link and email it to her myself. I don't see this anywhere in the API or the Sign user interface so I assume it is not possible, but I want to double check if there is any kind of workaround (beyond asking this person to let me rummage in her email).

    6 replies

    C
    Forum|alt.badge.img

    Hi Gabe,

    I couldn't find a way to get the sign URL for a specific user from the API. However there seems to be a way to at least change the email of the stuck recipient to an alternate email.

    Trying to replicate your use case...

    So I have a document where I request signing to 3 persons in a specific sequence.

    I can see on the sign request details on the box app, the email status and which one is pending. Note that for signers where a sequence is specified, the email request only goes out if the previous signer completed the request.

    This may justify why your user is complaining not getting the request, are you using a signer sequence and if so did the previous recipient actually completed the request?

    If there is something wrong with the user email, you can try to correct this on the request and use an alternate email for that recipient. The steps are fairly complex so please do try this on a test case first.

    Still on the request summary, open the revise request.

    You should be able to update the stuck recipient email to an alternate email. Press save.

    Again, try this first on a sample before proceeding.

     

    C
    Forum|alt.badge.img

    Hi Rui, thanks for looking into this for me. Yes, I am using a signing sequence, and I am also using templates with tags so that I can generate a request with a script using the API depending on the number of users. I have viewed the sign request details as you mention and yes the sequence has been completed up to this particular user. I will also try revising the request with this individual's alternative email address. I have tried that before and from what I recall I could not save the revision because the request had been generated using the template with tags. I will try again, though. If that doesn't work I will export the progress and then create a new request for the remaining individuals.

    C
    Forum|alt.badge.img

    Hi Gabe,

    Did it work?

    C
    Forum|alt.badge.img

    Unfortunately revising the request with the new email for the one signer does not work. I get an error message that the revision cannot be saved because other signers in the sequence cannot be modified. I don't know why that occurs. Possibly because the request was generated from a template with tags. I have cancelled the request, printed the partially complete document, scanned, then manually added the remaining signers.

    C
    Forum|alt.badge.img

    I glad you found a work around for this, however I do think it is worth investigating this particular use case/flow.

    I'll move this thread to the support forum and the support folks will try to follow up on this. Hope you do not mind and thanks for your patience.

     

    C
    Forum|alt.badge.img

    Did you get this resolved? It turns out you CAN get the url. In the signers array, each signer has a property called embed_url. But you need to do TWO things to utilize it and there are certain side effects.

    1) It can only be retrieved in the response when you initially create the signing request. It doesnt look like it's available afterwards so you get one shot at grabbing it.

    2) This field is only populated if you set the embed_url_external_user_id field of the signer during the request. Just set it to the user's email. However when you do this, it appears that Box's emails are suppressed and you have to send this link manually

    "embed_url": "https://example.com",
     
    Terms of ServiceAccessibility statement