3 ms·
You have definitely struck my curiosity - which version of this integration I outlined did you guys implement? 1. Embedded views + user creation w/o requiring
by inoda 8y ago
You have definitely struck my curiosity - which version of this integration I outlined did you guys implement?
1. Embedded views + user creation w/o requiring email confirmation
2. Embedded views with 1 API User
I don't want to assume anything here, but I think you either didn't build exactly what we were trying to, you are on the legacy version of their API, or you have that embedded view refresh bug I outlined live in prod.
- rblatz 8y agoI just checked we are using the v2 rest api. We create a user, we do not send them an email, we then add the documents and setup the envelope, then direct them to the user's embed signing room. I wish I could find the old postman POC since that would make it a lot easier for me to explain exactly our sequence of api calls.
- f0rgot 8y agoWe use v2 API as well and like rblatz said, we haven't ran into any problems. Our backend signs in to DocuSign as the main account. When a particular event requires it, the backend sends a POST to DocuSign and creates an envelope. In this POST request, we tell DocuSign that the user is going to be an embedded user. Once the envelope is created, we can ask for the "view url". In this request, we not only tell DocuSign to get us the vie URL for a specific signer (in case there are multiple signers), but we also tell DocuSign where we want the user to be redirected to after they are done signing. When this request returns, we will have a URL that we can redirect our end user to. Also, in terms of their documentation, I think it is fantastic in it thoroughness. All in all, I've had the opposite experience of OP.
- cagmz 8y agoThis is exactly how our integration works, as well.