Skip to navigation
Agreement Desk API 101

Agreement Desk API use cases

View as Markdown

You can use the Agreement Desk API to intake, review, and approve your agreements from a central hub Key use cases for Agreement Desk API include:

Centralized agreement intake and triage

A legal team intake and review a new client contract:

  1. An attorney emails your legal team with an agreement proposal. Your email box is configured as an intake for Agreement Desk.
  2. The Agreement Desk intake agent analyzes the email and attachments and suggests a type for the request, such as a master service agreement or a non-disclosure agreement. The agent also prepopulates the intake form with information extracted from the email and attachments.
  3. A reviewer confirms the request type, completes missing fields, and confirms the agreement request.
  4. The integration creates or updates a request with structured fields such as title, owner, due date, parties, region, contract value, and source-system ID.
  5. Documents are attached to the request and become part of its versioned record.

A legal team routes each agreement request to the right legal reviewer, reviews playbooks, and manages approvals:

  1. An agreement request is submitted, triggering a Workflow Builder or Agreement Manager workflow.
  2. The workflow sets the request status to Legal Review, then assigns the request owner based on agreement type, region, or business unit. It also adds Sales, Finance, or other stakeholders as followers.
  3. Legal reviews the draft in the centralized request workspace.
  4. AI-Assisted Review compares the document against the legal playbook, flags non-standard terms, and suggests alternative language.
  5. The attorney reviews, accepts, rejects, or edits the suggestions.
  6. Legal and Finance approvals are created and tracked.
  7. If revisions arrive, the latest document is uploaded as a new version and the request remains the audit source.
  8. After approval, the workflow changes the status to Ready for Signature.

Partner onboarding

A partner-management system initiates a partner agreement and risk-screening request:

  1. A partner-management system, such as Salesforce, starts onboarding for a prospective partner. It creates an agreement request containing the partner application, corporate information, a security questionnaire, evidence of insurance, any screening results, and a draft agreement.
  2. Partner Operations coordinates internal reviews by Finance, Security, Compliance, and Legal in Agreement Desk.
  3. Missing evidence or failed checks moves the request back to a state where the partner must provide additional information. If this missing information is later provided, it will resume review.
  4. After internal approval, the finalized agreement is passed to an external-facing workflow, such as through Workflows API, or directly to eSignature. The integration writes the signed agreement, diligence outcome, approval history, and completion timestamp back to the partner system and approved repository.

Next steps