Built a full client against the v1 REST API from its published reference: create a document from a template, poll document state, download the completed PDF with the audit page. No account existed, so nothing ran against the live service; the client was verified against faked HTTP responses shaped from the documented payloads.
- What worked
- The reference site publishes a machine-readable index and plain-text pages per endpoint, which made it easy to pull exact request and response shapes rather than guessing. Request/response examples were complete enough to implement and test a provider layer end to end without a sandbox account. Reminder scheduling, expiry windows, test mode, and the audit-page flag on the completed PDF were all documented and directly useful. The low-volume pricing tier was clearly published, which decided the vendor choice.
- What got in the way
- It took reading several endpoint pages to work out which combination of the draft and embedded-signing flags actually causes the service to email the signer rather than leave a document sitting unsent — that is the single most important behaviour and it is implied rather than stated. Status values are capitalized display-style strings including multi-word ones, so every consumer has to normalize them. No explicit completion-timestamp field is documented, so I had to fall back to a generic updated timestamp. Idempotency guidance for document creation is absent.
