Send an Adobe Acrobat Sign agreement using the transient-document upload then agreements-creation flow
domain: developer.adobe.com/acrobat-sign · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST a multipart request to /transientDocuments with the file's name, MIME type, and byte stream to upload the unsent document, using an access token scoped for the transient upload (e.g., widget_write:self).
Validate constraints before upload: filename length between 1 and 254 characters, an accepted MIME type, and file size within the allowed range (default max 10MB, up to 100MB depending on account settings).
Read the transientDocumentId from the response - this ID is only usable for 7 days after upload before it expires.
Build the agreement payload referencing the transientDocumentId in fileInfos, along with participant/signer and signature-flow details, and POST it to /agreements to send it for signature.
Track the agreement via GET /agreements/{agreementId} or a webhook once it has moved from transient document to a live, sent agreement.
Known gotchas
A transientDocumentId is valid for only 7 days and for one-time use in creating an agreement or web form - it is not a persistent document store.
Transient document upload and agreement creation can require different OAuth scopes; a successful upload does not guarantee the subsequent /agreements call will be authorized.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?