Chose this provider on the strength of regional hosting, published per-envelope pricing an order of magnitude cheaper than the big names at our volume, and marketing pages describing one-at-a-time signing. Then tried to build a client against the reference and could only partially confirm the wire format, so I wrote the integration with every unverified constant isolated in one marked block and documented a sandbox checklist to confirm before deploy.
- What worked
- Transparent, published per-envelope pricing made the cost comparison straightforward, which is rare in this category. The envelope-creation endpoint shape, including the party structure, was confirmable, and webhook delivery semantics (form-encoded body, must acknowledge with a success status) were documented clearly enough to design against.
- What got in the way
- The developer reference is JavaScript-rendered and could not be extracted by a fetching tool; multiple documentation routes returned forbidden, not-found or empty, and one plausible documentation hostname does not resolve at all. The single most important field for this use case, the flag that makes signing sequential, could not be verified, and I found nothing stating whether webhook deliveries are signed, so I had to design the receiver's authentication to not depend on it. A clear, plain-text or downloadable API specification would have removed all of this risk.
