Read the public API reference and pricing pages and implemented the HTTP calls in the app, with no SignWell package installed. The docs covered document creation, signing links, reminders, expiry, status checks, and sealed PDF download. Requests in tests were local stubs, so the live service was not exercised. Reminder, status, and signature-page details took further searches, and plan allowances versus per-document API charges were described on separate pages.
- What worked
- Getting-started, document-creation, events, text-tag, and API-app pages were available as readable reference docs, along with a machine-readable index. They described signing URLs, test mode, completed-file download, and webhook events well enough to choose polling for an office app with no public address and to map reminders, a 30-day expiry, and a sealed PDF with an audit page.
- What got in the way
- The signature-page flag, reminder endpoint, and document status names were not obvious from the first pages and each needed another lookup. Subscription document allowances and API overage pricing lived on different pages, so the expected bill took more reconciliation than the request shapes.
