The OpenAPI document describes paths, request shapes and response schemas for API v1. Use it as a concrete input to tooling, while reading the workflow guides for behaviors such as asynchronous PDF rendering and webhook recovery.
Download the document
The service publishes its contract at api.waiver.com/openapi.json. This documentation also includes a downloadable snapshot reviewed on September 11, 2026. The snapshot contains 35 paths and 42 HTTP operations.
Store the version of the schema used for a generated client with your integration's build inputs. That makes it possible to explain why a generated type differs from a later contract rather than regenerating silently during an unrelated deployment.
Generate, then inspect
Choose a generator suitable for your language and review the resulting authentication configuration, optional fields and response parsing. Do not commit a live key in a generated example or shared collection.
Generated types help catch shape errors. They do not decide whether a retry is safe or whether an expired waiver should permit admission. Those decisions depend on the endpoint and the operation around it.
Account for binary and asynchronous results
PDF downloads return binary content when ready. Signed records can exist before their PDF has finished rendering. Make sure the generated client can handle the binary response and that the worker respects readiness rather than assuming every successful sign immediately yields a downloadable file.
Read error responses through the common error envelope. Validate how your chosen client exposes response headers, especially request IDs, rate-limit information and retry-after.
Review changes deliberately
Compare contract updates before adopting them. Check newly required fields, enum handling and any operation your integration uses. Unknown optional response fields should not crash a parser that only needs a stable subset.
Run your own integration checks against representative responses and authorized test data. The endpoint examples on this site are illustrative and are not a hosted API console. Start with the quickstart, then choose the resource references that match your workflow.