Obtain a Bearer token by POSTing to /oauth2/token with grant_type=password and your user credentials, or use client_credentials for a service account.
Upload the PDF via POST to /document (multipart/form-data); capture the document id from the response.
Add signature fields to the document by POSTing to /document/{id} with a fields array specifying each field's type, page number, coordinates, and the signer's role.
POST to /document/{id}/invite with a to array of signer objects (email, role_id, order) and a from sender email to dispatch the signing invitation.
Retrieve the completed document via GET /document/{id}/download?type=merged once the signing status shows completed.
Known gotchas
Password-based OAuth tokens have a short expiry; implement token refresh using the refresh_token grant to avoid mid-workflow 401 errors.
Field coordinates are in points relative to the PDF page origin; misaligned fields are a common cause of signer confusion — validate placements in the web UI first.
The free plan limits the number of documents per month and disables certain API features; check your plan's API entitlements before building production flows.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp