3 ms·
I've done a docusign implementation, and I don't really agree with them. Their API is fine honestly, I think their documentation could be better and some things
by ecshafer 8y ago
I've done a docusign implementation, and I don't really agree with them. Their API is fine honestly, I think their documentation could be better and some things are named awkwardly. But the implementation really isn't hard, my only real complaint is that when we did it they pushes the DocuSign connect service really hard, which honestly was kind of a waste and didn't live up to many of their promises, but that's normal b2b upselling. It's a normal API, and definitely not as bad as this person makes it seem.
- Bamafan 8y agoWhether an API is "good" or "bad" often is dependent on the requirements of the calling client. At the beginning of projects when client requirements are unclear, it is often hard to determine whether a supporting API/library truly meets your needs.
- ecshafer 8y agoThat is true. To move away from language like good or bad. I would say DocuSign is quite reliable, we had one outage that was their fault and we were an edge case. I would also say that their API is sufficient for 95% of use cases or more with very little work arounds. Their customer success architects or whatever they call them were also pleasant to work with and responded promptly.