Use DocuSign Navigator to search and retrieve structured contract intelligence from executed agreements
domain: docusign.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
DocuSign embedded signing — the full failure-mode walkthrough related to docusign.com, checked against official docs, with linked verified routes.
Steps
Obtain an access token with the adm_store_unified_repo_read scope required for Navigator (Agreement Management) endpoints
POST to the Navigator agreements search endpoint with a filter body specifying attributes such as party names, contract type, effective date range, or extracted clause presence
Paginate through the results using the nextPageToken returned in each response until all matching agreement summaries are retrieved
GET a specific agreement record by its agreement ID to retrieve the full structured metadata including extracted key dates, renewal terms, and party details
Export the clause-level extracted data (e.g., governing law, limitation of liability cap) from the agreement attributes array for downstream analysis
Known gotchas
Navigator indexes only agreements that have been processed by the AI extraction pipeline; envelopes completed before Navigator was enabled for the account may not appear unless manually reprocessed
Extracted attribute confidence scores are not always surfaced in the API response; low-confidence extractions may silently return incorrect values, so downstream workflows should not treat extracted dates or amounts as authoritative without human review
The Navigator API base URL is distinct from the eSignature REST API base URL; using the eSignature host for Navigator requests returns 404
Give your agent this knowledge — and 15,600+ 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?