1/21/2024 0 Comments Docusign pricing vs echosignBut the code stayed up there for a long time. They responded with a something along the lines of ya, we had the java guy do that. I felt so bad that I emailed them some suggested fixes and asked if they had python experience. I think this particular bit of code is gone now, but it was incredible. It was the messiest python code I had ever seen. They built their json paylod by concatenating text. The person also seemed to not be aware of a dictionary. Every line ended with a semicolon (in python this is not an error, but is officially discouraged). I am not trying to be mean, it was that bad. It was clear that the person who wrote it had no experience with python at all. The python example was a total embarrassment. They had a some API examples in different languages for their docs. The rep told me in a very condescending way that it template ID was part of the URL. It was not listed anywhere on the developer dashboard. I remember having to call them asking where to find a template ID so I could save that and send out the proper doc to customers. There were some very strange things going on with their API. I had a project that used docuSign a few years ago. I honestly believe I can summarize this whole article as: Dev takes first steps into OAuth and gets lost. I highly doubt the refresh token expired in an hour, but hey - I haven't used it so maybe I'm wrong. >I got this working, but it took some janky work to re-work the JWT flow to manage hourly expiring tokens for all of our user that choose to enable the esignature feature. ![]() You should be making the request with the token of the delegated user, not a generic account. This honestly sounds like they were politely telling you that you haven't implemented OAuth correctly. About a week later, we were informed that this is intentional, and they were worried about breaking anyone that is using this as a feature. >Someone on the team noticed that if you refresh the page, you get logged in as the user that was making the API request. This actually sounds like the author is lost because they don't understand OAuth again (and to be fair, I've implemented OAuth and it's easy to get wrong). I haven't used it, so maybe it's terrible, but I'm suspicious of the author at this point.īut no discussion of why, or what he would expect instead. ![]() They appear to support a fully fledged OAuth implementation ( ). >I was annoyed that they didn’t provide a secret key to authorize API requests Maybe the goal here wasn't to be technical (although I'm not sure why given it's an article about docusign api integration) but this is a WHOOOOOLE lot of text with basically nothing worth reading. HelloSign's API is a first class citizen whereas DocuSign's felt more like an afterthought. But if you're trying to wrap an e-sign provider within your application, I would recommend HelloSign 1000x. Obviously, they have a large user base and I'm sure most of them are at least satisfied, if not happy. I hope this clarifies some of the technical problems we were trying to solve for.Įdit - I'm sure DocuSign can solve for some use cases. By then, we had had such a poor experience with non-answers from their team that we called it quits. ![]() The issue was their “regular” user creation flow involves a email going out to the user to confirm - obviously this is unideal if our goal was to wrap DS and hide it’s existence as much as possible from users.ĭocuSign offered a workaround for this, which involved basically getting shifted to a legacy version of the API, with no hard promise of it not being sunsetted. But we still wanted to hide this process from our users, keeping DS as embedded as possible. You now can click around the entire account - viewing any data that belongs to the API user (in our case, all of the data).Īt this point (as the OP called out), we realized we had no choice but to create DS users. Go to an embedded page, authenticated as the “API user” (which looks like you’re sandboxed within DS to the embedded page)ģ. We were looking for using 1 “API user” to make requests, handling data scoping ourselves within the application.ġ. We wanted to avoid having to create a DS user for every user in our application that turned on this feature. We wanted to use their embedded flows, to keep the experience within our application as much as possible.Ģ. I was on this project and can speak a bit more on the technical details here.ġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |