Query Agreement Data with the Docusign Agreement Manager API or MCP Server

Key takeaways: 

• Use the Agreement Manager API to programmatically retrieve, filter, and integrate structured agreement data into applications, dashboards, and workflows.

• Use the Docusign MCP Server to query agreement data through natural language and support more dynamic, agentic interactions.

• The Agreement Manager API is best suited for structured, repeatable tasks, while the MCP Server is useful for ad-hoc queries and AI-assisted workflows.

• Both approaches give developers ways to access agreement insights outside the Docusign UI, depending on how predictable and interactive the use case is.

Docusign Agreement Manager uses AI to analyze agreements and extract structured information such as document types, parties, expiration dates, and key terms. It identifies document types, extracts parties, surfaces expiration dates, and highlights key terms without requiring manual tagging or setup.

The challenge with large agreement repositories is that contract language isn’t always consistent, which makes simple keyword-based retrieval unreliable. For example, an employee looking for all active NDAs might search “NDA” in a contract repository. But an agreement labeled “confidentiality agreement” rather than “NDA” or “non-disclosure agreement” could be easy to miss.. 

With the help of AI, Agreement Manager can categorize a contract based on its content and structure. It then extracts details like:

• Agreement status

• Parties involved

• Effective and expiration dates

• Key obligations and terms

This information is available in the Docusign UI, but developers can also access agreement data through the Agreement Manager API and the Docusign MCP server.

Agreement Manager API vs. MCP Server: Which should you use?

Use the Agreement Manager API for structured, repeatable integrations and the Docusign MCP Server for natural-language, agentic, or ad-hoc interactions with agreement data. The best approach depends on how predictable your workflow is and how users need to interact with the data.

The Agreement Manager API is good for repeatable, structured tasks. For example, if you need to run the same query on a regular schedule or move large amounts of data between systems, an API integration provides a predictable interface.

The Docusign MCP Server is useful for ad-hoc natural-language queries and agentic workflows where the interaction may vary based on context.

Query Agreement Data Through the Agreement Manager API

While the Agreement Manager UI provides a convenient way to browse and search agreements, the Agreement Manager API lets developers access agreement data programmatically for use in applications, dashboards, reports, and other integrations. You can also use the API to bulk upload agreements to the Agreement Manager repository for AI-assisted analysis.

Retrieve a list of agreements

To export and sync data from all of your agreements, call the Agreements: getAgreementsList endpoint. 

const requestUrl = `https://api-d.docusign.com
/v1/accounts/${accountId}/agreements`;
   const res = await fetch(requestUrl, {
     method: 'GET',
     headers: {
       'Authorization': `Bearer ${accessToken}`,
       'Accept': 'application/json',
       'Content-Type': 'application/json'
     }
   });

You’ll get back a JSON response with structured insights about all of your agreements, similar to the example below:

[
  {
    "id": "7ee4b8f4-xxxx-xxxx-xxxx-4426968b5f0f",
    "title": "Non-Disclosure Agreement",
    "file_name": "NDA.docx",
    "document_id": "c1cfba00-xxxx-xxxx-xxxx-07843105ea83",
    "type": "Nda",
    "category": "BusinessServices",
    "status": "COMPLETE",
    "review_status": "PENDING",
    "parties": [
      {
        "id": "7751d7a6-xxxx-xxxx-xxxx-42b468c16ce0",
        "name_in_agreement": "ByCo Ltd"
      },
      {
        "id": "b9133ef6-xxxx-xxxx-xxxx-1cbf0f1cd233",
        "name_in_agreement": "Fontara Services Inc"
      }
    ],
    "provisions": {
      "effective_date": "2023-06-07T00:00:00",
      "expiration_date": "2026-06-06T00:00:00",
      "execution_date": "2023-06-21T00:00:00",
      "term_length": "P3Y",
      "confidentiality_obligation_period": "P3Y",
      "jurisdiction": "California",
      "nda_type": "ONE_WAY",
      "renewal_type": "FIXED_TERM",
      "renewal_notice_date": "2026-06-06T00:00:00"
    },
    "custom_provisions": {},
    "related_agreement_documents": {},
    "languages": [
      "en"
    ],
    "source_name": "UploadCenter",
    "source_id": "c1cfba00-xxxx-xxxx-xxxx-07843105ea83",
    "source_account_id": "0820f9c5-xxxx-xxxx-xxxx-8a0df87f44aa",
    "metadata": {
      "created_at": "2026-07-02T20:30:40.710922+00:00",
      "created_by": "s2s:admi/admi-iam-transforms",
      "modified_at": "2026-09-10T02:27:50.41976+00:00",
      "modified_by": "s2s:admi/admi-iam-transforms"
    },
    "_links": {
      "document": {
        "href": "https://s1.us.services.demo.docusign.net/document-public-dms/v1/accounts/0820f9c5-xxxx-xxxx-xxxx-8a0df87f44aa/documents/c1cfba00-xxxx-xxxx-xxxx-07843105ea83"
      },
      "agreement_types": {
        "href": "/v1/accounts/0820f9c5-xxxx-xxxx-xxxx-8a0df87f44aa/agreement-types"
      }
    }
  }
]

Filter agreements

When you're working with thousands of agreements, filtering becomes essential. The API supports parameters that let you narrow results to specific agreement types, date ranges, parties, or other criteria.

For example, you can add a query parameter to your GET request to filter agreements by agreement type.

const requestUrl = `https://api-d.docusign.com
/v1/accounts/${accountId}/agreements?type=Nda`;
   const res = await fetch(requestUrl, {
     method: 'GET',
     headers: {
       'Authorization': `Bearer ${accessToken}`,
       'Accept': 'application/json',
       'Content-Type': 'application/json'
     }
   });

The API also supports OData filters and full-text search for more complex queries. For example, to search for agreements containing the text “Non-Disclosure Agreement,” you can set $search="Non-Disclosure Agreement".

You can find the full documentation for filtering agreements in the API reference.

Query agreement data with the Docusign MCP Server

While the API excels at structured, repeatable tasks, there are scenarios where you want more flexibility. You might want to ask questions in natural language, explore data dynamically, or build AI agents that can reason about agreements and take action.

The Docusign MCP Server lets supported AI assistants interact with Docusign agreement data and capabilities using natural language. Instead of writing code to call individual API endpoints, users can ask questions or request actions through an AI assistant, which uses the MCP Server to interact with Docusign. The server provides access to the Agreement Manager API, alongside tools from the eSignature REST API and other Docusign features.

Example: Find agreements that are expiring soon

A contract manager might need to find agreements that are expiring soon to prepare for upcoming renewals. They can query the MCP server with natural language to get that information, simply by asking, "Which of my Docusign agreements are expiring soon?"

In the background, the Agreement Manager API powers the query, filtering for agreements with upcoming expiration dates, and returning a formatted response:

The MCP server gives users access to Docusign data where they’re already working, reducing the friction that comes from context-switching.

Start building

You can get started with the Agreement Manager API by signing up for a Docusign developer account. Then, start making API calls in the language of your choice. You can use one of our IAM SDKs in C#, Java, or TypeScript, or set up the Agreement Manager API Postman collection and start testing API requests there.

To get started with the Docusign MCP Server, review the available MCP tools and connect a supported AI assistant. From there, you can begin querying agreement data and incorporating Docusign capabilities into AI-assisted workflows.

Related resources

• Agreement Manager API reference

• Docusign OAuth and authentication 

• Docusign MCP overview and docs 

• Postman collections and examples