Conga

Supergood | Conga API

Alex Klarfeld

Alex Klarfeld

— 7 min read
Supergood | Conga API

Programmatically access agreements, templates, clauses, negotiations, approvals, signatures, and obligation tracking from Conga with a stable REST API. Supergood builds and operates production-grade, unofficial Conga integrations so your team can automate CLM and revenue workflows without heavy custom engineering.

Plain English: Conga is contract lifecycle management and document generation software used by sophisticated in-house legal teams to intake agreement requests, draft using templates and clause playbooks, negotiate and redline, manage approvals, execute via eSignature, store executed contracts, and track obligations and renewals. An unofficial API lets you pull agreement records, versions, approval queues, and signature packets—and push new requests, upload drafts, submit approvals, initiate eSign, and create obligations tied to matters.

For a tech company integrating with Conga—especially one fitting into a customer’s iManage workflow—this means you can sync matter folders and contract documents between Conga and iManage, enrich Conga records with matter metadata, ingest negotiation versions and redlines into your review tools, and publish executed copies back to iManage automatically. You can build features like intake forms that create draft agreements in Conga, iManage-aware approval routing, clause analytics dashboards, obligation reminders tied to matters, and unified contract repositories spanning Conga, Salesforce, and iManage.

What is Conga?

Conga (https://www.conga.com) provides Contract Lifecycle Management (CLM), document generation, workflow orchestration, and eSignature across the revenue and legal lifecycle. It centralizes agreement drafting and negotiation, manages clause libraries and templates, routes approvals, executes signatures, and tracks post-signature obligations and renewals. Conga commonly integrates with Salesforce and enterprise systems used by legal and commercial teams.

Core product areas include:

  • Contract Lifecycle Management & Repository (Agreement records, statuses, versions)
  • Document Generation & Templates (Conga Composer, guided drafting)
  • Clause Library & Playbooks (Preferred language, fallbacks, risk ratings)
  • Negotiation & Redlining (Version control, compare, comments)
  • Approvals & Workflow Orchestration (Steps, conditions, escalations)
  • eSignature (Conga Sign, recipient routing, completion certificates)
  • Obligations & Renewals (Key terms, milestones, alerts, tasks)
  • Revenue & Quote-to-Cash (CPQ, pricing, quote-to-contract handoff)

Common data entities:

  • Agreements (Master agreements, NDAs, MSAs, SOWs, amendments, renewals)
  • Counterparties (Organizations and contacts, addresses, identifiers)
  • Templates & Clause Library (Template IDs, clause variants, fallback logic)
  • Versions & Redlines (Drafts, comparisons, comments, authors)
  • Approvals (Steps, assignees, status, actions, timestamps)
  • Signatures (Recipients, routing order, completion status, envelopes)
  • Documents (Drafts, executed PDFs, certificates, attachments)
  • Obligations & Milestones (Type, due date, owner, status)
  • Users/Roles & Teams (Permissions, queues)
  • Audit Events (Who did what, when, before/after values)

The Conga Integration Challenge

Legal teams rely on Conga and iManage side-by-side, but translating portal-centric CLM into API-driven automation presents challenges:

  • Versioning & redlines: Negotiation produces multiple drafts, compares, and comments that must be normalized and correlated to matters
  • Clause playbooks: Preferred clause selection and fallback logic need consistent metadata mapping across templates and versions
  • Long-running workflows: Approvals and signatures can span hours or days; APIs must handle asynchronous states and retries
  • Identity & auth complexity: SSO/MFA, Salesforce-backed tenants, and session lifecycles complicate headless automation
  • Entitlements & segregation: Role-based access, team queues, and document visibility must be respected
  • Document routing: Executed files and certificates must land in the correct iManage workspace, folder, and version scheme
  • Audit rigor: Every action—approvals, clause swaps, signature—requires immutable, traceable records

How Supergood Creates Conga APIs

Supergood reverse-engineers authenticated browser flows and network interactions to deliver a resilient API endpoint layer for your Conga tenant.

  • Handles username/password, SSO/OAuth, and MFA (SMS, email, TOTP) securely
  • Maintains session continuity with automated refresh and change detection
  • Normalizes agreement, version, approval, signature, and obligation objects
  • Aligns with customer entitlements and role-based permissions to ensure compliant access
  • Supports high-volume operations (bulk agreement intake, approvals) with polling or webhooks for long-running jobs
  • Offers iManage-aware adapters for document routing and matter metadata sync

Use Cases

  • Push new agreement requests tied to iManage matter numbers
  • Generate first drafts from templates and clause playbooks
  • Persist agreement metadata and executed documents back to the right iManage workspace and folder

Negotiation & Redline Synchronization

  • Upload new versions and capture redline metadata
  • Compare drafts and expose comments and change summaries via API
  • Maintain a normalized revision history across Conga and your platform

Approval Routing & eSignature Execution

  • Sync approval queues into your case management or workflow tool
  • Record decisions and audit trails back to Conga
  • Initiate Conga Sign envelopes, retrieve completion certificates, and archive to iManage

Obligations, Renewals & Compliance Dashboards

  • Register obligations from executed terms with owners and due dates
  • Deliver reminders and status updates via webhooks
  • Aggregate KPIs across agreements and counterparties for reporting

Available Endpoints

Authentication

POST /sessions: Establish a session using credentials. Supergood manages MFA (SMS, email, TOTP) and SSO/OAuth when enabled. Returns a short-lived auth token maintained by the platform.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/sessions \
  --header 'Authorization: Basic <Base64 encoded token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "username": "[email protected]",
    "password": "<password>",
    "mfa": { "type": "totp", "code": "123456" }
  }'

Example response

{
  "authToken": "eyJhbGciOi...",
  "expiresIn": 3600,
  "user": {
    "id": "u_cnga_12ab34",
    "name": "Legal Ops",
    "entitlements": ["agreements", "approvals", "signatures", "obligations"]
  }
}

POST /sessions/refresh: Refresh an existing token to keep sessions uninterrupted.

Agreements

POST /agreements: Create or update an agreement record, generate a first draft from a template, and optionally link to an iManage matter/workspace.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/agreements \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "externalId": "agr_0009812",
    "title": "Master Services Agreement - Acme",
    "type": "MSA",
    "accountId": "acct_4920",
    "counterparty": {
      "organizationName": "Acme Corp",
      "primaryContact": {"name": "Dana Lee", "email": "[email protected]"}
    },
    "templateId": "tmpl_msa_v5",
    "status": "draft",
    "effectiveDate": null,
    "termMonths": 36,
    "tags": ["priority", "enterprise"],
    "matter": {
      "iManageWorkspaceId": "IMW-73218",
      "matterNumber": "MAT-2026-0412"
    }
  }'

Example response

{
  "agreementId": "agr_cnga_9f12a7",
  "status": "draft",
  "version": {
    "versionId": "ver_01",
    "generatedFromTemplate": true,
    "documentId": "doc_8a2b71",
    "createdAt": "2026-02-20T10:03:11Z"
  },
  "links": {
    "iManageWorkspaceId": "IMW-73218"
  }
}

Versions & Negotiation

POST /agreements/{agreementId}/versions: Upload a new draft version during negotiation, capture redline metadata, and optionally associate with an iManage document.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/agreements/agr_cnga_9f12a7/versions \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "uploadToken": "upl_7fa223",
    "comment": "Counterparty returned v2 with indemnity edits",
    "compareAgainstVersionId": "ver_01",
    "redline": {"changesCount": 17, "hasClauseSwaps": true},
    "iManageDocumentId": "IMD-441097"
  }'

Example response

{
  "versionId": "ver_02",
  "status": "in_review",
  "redlineSummary": {
    "additions": 6,
    "deletions": 5,
    "modifiedClauses": ["Indemnity", "Limitation of Liability"],
    "comments": 12
  },
  "documentId": "doc_91c003",
  "createdAt": "2026-02-20T11:20:44Z"
}

Approvals

GET /approvals: List approval steps with filters for status, step name, assignee, and update windows.

Query parameters

  • status: pending | approved | rejected | skipped
  • step: legal | finance | executive | custom
  • assigneeId: string
  • agreementId: string
  • updatedFrom, updatedTo: ISO 8601 timestamps
  • page, pageSize: integers for pagination

Example response

{
  "items": [
    {
      "approvalId": "apv_7b120e",
      "agreementId": "agr_cnga_9f12a7",
      "step": "legal",
      "status": "pending",
      "assignee": {"userId": "u_cnga_12ab34", "name": "Legal Ops"},
      "dueAt": "2026-02-21T17:00:00Z",
      "createdAt": "2026-02-20T11:21:03Z",
      "updatedAt": "2026-02-20T11:21:03Z"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

PATCH /approvals/{approvalId}: Submit an approval decision with rationale and optional attachments.

curl --request PATCH \
  --url https://api.supergood.ai/integrations/<integration_id>/approvals/apv_7b120e \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "status": "approved",
    "rationale": "Clause swaps aligned with playbook tier B; indemnity cap acceptable.",
    "attachments": [
      {"fileName": "risk-analysis.pdf", "uploadToken": "upl_09aa51"}
    ]
  }'

Example response

{
  "approvalId": "apv_7b120e",
  "status": "approved",
  "approvedAt": "2026-02-20T14:15:12Z",
  "updatedBy": {"userId": "u_cnga_12ab34", "name": "Legal Ops"}
}

Signatures

POST /agreements/{agreementId}/sign: Initiate an eSignature envelope via Conga Sign, define recipients and routing order, and receive completion updates.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/agreements/agr_cnga_9f12a7/sign \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "documentId": "doc_91c003",
    "recipients": [
      {"role": "customer_signer", "name": "Dana Lee", "email": "[email protected]", "order": 1},
      {"role": "company_signer", "name": "Sam Patel", "email": "[email protected]", "order": 2}
    ],
    "options": {"reminders": true, "expiresInDays": 14},
    "archive": {"iManageWorkspaceId": "IMW-73218", "folder": "Executed"}
  }'

Example response

{
  "envelopeId": "env_csign_5c601a",
  "status": "sent",
  "recipients": [
    {"email": "[email protected]", "status": "pending"},
    {"email": "[email protected]", "status": "pending"}
  ],
  "callbacks": {
    "completion": "https://api.supergood.ai/webhooks/<integration_id>/signatures/completion"
  }
}

Get full API Specs →

Technical Specifications

  • Authentication: Username/password with MFA (SMS, email, TOTP) and SSO/OAuth where enabled; supports service accounts or customer-managed credentials
  • Response format: JSON with consistent resource schemas and pagination across modules
  • Rate limits: Tuned for enterprise throughput while honoring customer entitlements and usage controls
  • Session management: Automatic reauth and cookie/session rotation with health checks
  • Data freshness: Near real-time retrieval of agreements, versions, approvals, signatures, and obligations
  • Security: Encrypted transport, scoped tokens, and audit logging; respects Conga role-based permissions and tenant boundaries
  • Webhooks: Optional asynchronous delivery for long-running workflows (e.g., approval decisions, signature completion)

Performance Characteristics

  • Latency: Sub-second responses for list/detail queries under normal load; approval and signature completion reflect underlying platform behavior
  • Throughput: Designed for high-volume intake, negotiation version uploads, and approval queue synchronization
  • Reliability: Retry logic, backoff, and idempotency keys minimize duplicates and support at-least-once processing
  • Adaptation: Continuous monitoring for UI/API changes with rapid adapter updates

Getting Started

  1. Schedule Integration Assessment

Book a 30-minute session to confirm your modules, licensing, and authentication model.

  1. Supergood Builds and Validates Your API

We deliver a hardened Conga adapter tailored to your workflows and entitlements.

  1. Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Conga evolves.

Schedule Integration Call →

Frequently Asked Questions

Q: Which Conga modules can this integration cover?

Supergood supports workflows commonly used for CLM, including Agreements & Repository, Templates & Clause Library, Negotiation Versions, Approvals & Orchestration, eSignature (Conga Sign), and Obligations/Renewals, subject to your licensing and entitlements. We scope coverage during integration assessment.

Q: How are MFA and SSO handled for automation?

We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. Sessions are refreshed automatically with secure challenge handling and monitoring for session expiry.

Q: Do you support iManage syncing?

Yes. We can link Conga agreements and documents to iManage workspaces and folders, push executed PDFs and certificates to the correct matter, and keep metadata synchronized via webhooks or polling.

Q: How do you standardize versions and redline data?

We normalize version identifiers, compare results (additions/deletions, clause modifications), comments, and authors into a consistent schema while preserving raw source artifacts for audit.

Q: Can we initiate and track eSignature via Conga Sign?

Yes. We support envelope creation, recipient routing, reminders/expiry options, status polling, and completion callbacks, with automatic archiving to iManage when configured.

Q: Do you work with Salesforce-native deployments?

Yes. We adapt to Salesforce-backed Conga tenants, handle environment-specific URLs, profiles, and entitlements, and operate within your governance model.

Ready to automate your Conga workflows?

Supergood can have your Conga integration live in days with no ongoing engineering maintenance.

Get Started →

Read more