canonical: https://jentic.com/apis/concordnow.com/concordnow

# Concordnow Concord

Concord is a contract lifecycle management platform with unlimited e-signatures and contract storage. The API exposes the resources behind the Concord interface so teams can create, edit, sign, and manage agreements from outside the product. It covers agreements, folders, signatures, automated templates, organization members and groups, clauses, tags, branding, reports, and webhooks. Sandbox and production environments are available for testing and live integration.

## For AI agents

Manage Concord agreements end to end: draft from templates, route for signature, store in folders, expose clauses and metadata, and listen for lifecycle events.

## Scope

Does not handle CRM opportunity tracking, billing, or HR onboarding - use for contract lifecycle, e-signature, and clause governance only.

## Capabilities

- Create an agreement from an automated template and populate its merge fields
- Route an agreement for signature and track signer status to completion
- Organize agreements into folders and apply tags for retrieval
- Maintain a reusable clause library and inject clauses into agreements
- Manage organization members, groups, and invitations to control access
- Subscribe to webhooks for agreement and signature lifecycle events
- Generate reports across the agreement portfolio for renewals and obligations

## Use cases

### Sales Contract Automation

Generate a sales contract from a Concord automated template the moment a deal hits closed-won, populate the buyer's details, and route it for signature. The `/organizations/{organizationId}/agreements` endpoints handle creation and metadata, and the signature endpoints push the agreement to signers. Revenue operations teams use this to remove the manual hand-off between CRM and the legal team.

Example prompt: Generate an agreement from template T-MSA for buyer Acme Inc with values name, address, and amount, then send it for signature to two named signers

### Agreement Repository and Renewals

Use Concord as the system of record for executed contracts, including renewal and obligation tracking. Folder, tag, and metadata endpoints organize agreements, while reporting endpoints expose upcoming expiries. Procurement and legal-ops teams query the API to feed renewal dashboards and surface termination windows before they pass.

Example prompt: List all agreements with metadata field 'autoRenew' equal to false expiring in the next 60 days and tag them 'renewal-review'

### Lifecycle Event Webhooks for Downstream Systems

Push agreement lifecycle events into a CRM, billing system, or finance close process. The Webhooks resource lets agents subscribe to events such as agreement.created, signature.completed, and agreement.expired and receive structured payloads. This avoids polling and keeps the downstream system synchronized with Concord state.

Example prompt: Subscribe a webhook with URL https://app.example.com/hooks for signature.completed events on the legal organization and verify the signing secret

### Clause and Branding Governance

Govern the language used across every agreement by managing the clause library and custom branding centrally. The Clause Library resource stores approved clauses for legal review, and Custom Branding endpoints control logo and color usage on outbound documents. In-house counsel teams use this to enforce consistent language without auditing every agreement individually.

Example prompt: Add an updated indemnification clause to the clause library, then list all agreements that still reference the previous version

### Agent-Driven Contract Operations via Jentic

Let an AI assistant handle contract drafting and routing for sales or procurement teams in chat. Through Jentic the agent searches by intent, loads the Concord operation schema, and executes the call without the developer wiring auth or pagination. This collapses the manual step where a salesperson asks legal-ops to spin up a contract.

Example prompt: On the prompt 'send the standard NDA to alex@partner.com', generate an agreement from the NDA template with that signer, send it for signature, and return the agreement uid

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/organizations/{organizationId}/agreements` | Create an agreement |
| GET | `/user/me/organizations/{organizationId}/agreements` | List agreements visible to the calling user |
| POST | `/organizations/{organizationId}/agreements/{agreementUid}/versions/upload` | Upload a new version of an agreement |
| GET | `/organizations/{organizationId}/agreements/{agreementUid}.pdf` | Download the PDF of an agreement |
| POST | `/organizations/{organizationId}/agreements/{agreementUid}/comments` | Add a comment to an agreement |
| GET | `/organizations/{organizationId}/agreements/{agreementUid}/metadata` | Retrieve agreement metadata |
| GET | `/user/me/organizations/{organizationId}/folders` | List folders for the calling user |

## Key resources

- **Agreements** — Agreement creation, versions, metadata, fields, attachments, and exports
- **Signature** — Send-for-signature flow and signer status
- **Automated Templates** — Reusable contract templates with merge fields
- **Folders and Tags** — Organize agreements for retrieval
- **Clause Library** — Reusable approved clauses for legal review
- **Organization, Members, and Groups** — Tenant, user, and access management
- **Custom Branding** — Logo and color configuration on outbound documents
- **Webhooks and Events** — Outbound subscriptions for lifecycle events
- **Reports** — Aggregate views over the agreement portfolio

## Why Jentic

- **Setup:** Wiring Concord by hand means learning its API key scheme, mapping its organization, agreement, and version resources, and handling document uploads and PDF retrieval yourself. Through Jentic you install once, import Concord from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Concord puts the organization and agreement ids in the URL path (`/organizations/{organizationId}/agreements/{agreementUid}`), so a rule can pin your agent to one organization or agreement. You choose the operations it may call, so you can allow reading agreements and posting comments while leaving version uploads out unless you add them.
- **Credential handling:** Your Concord API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a contract' or 'download an agreement PDF', and Jentic returns the matching Concord operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **PandaDoc** — Document automation platform with templates, e-signature, and CPQ-style pricing
- **BoldSign** — E-signature API focused on signing flows and templates
- **Xodo Sign (Eversign)** — E-signature API with template and document fields

## FAQ

### What authentication does the Concord API use?

The API uses an API key passed in the X-API-KEY header. You generate keys from your Concord account, and a missing or invalid key returns 401 Unauthorized. Through Jentic the key is stored encrypted in the vault and injected at execution time, so the raw key never enters the agent's prompt or logs.

### Can I send an agreement for signature with the Concord API?

Yes. Create the agreement under `/organizations/{organizationId}/agreements`, then use the Signature resource to route it to signers. Signer status is exposed on the agreement summary and lifecycle endpoints, and signature.completed events fire to subscribed webhooks.

### What environments does the Concord API offer?

Concord exposes a sandbox at https://uat.concordnow.com/api/rest/1/ and production at https://api.concordnow.com/api/rest/1/. Use the sandbox for testing API key flows and template creation before pointing your integration at production.

### What are the rate limits for the Concord API?

Concord applies tenant-specific rate limits and uses standard 4xx/5xx HTTP responses for errors, including 429 for throttling when bulk operations exceed your plan. Agents should add backoff on HTTP 429; Jentic surfaces these as structured errors rather than retrying silently.

### How do I create an agreement from a template through Jentic?

Run the Jentic search query 'create a Concord agreement from a template', load the returned operation, and execute it with the template id, organization id, and merge-field values. The created agreement uid is returned for follow-up signature and metadata calls.

### Can I export an agreement as a PDF?

Yes. GET `/organizations/{organizationId}/agreements/{agreementUid}.pdf` returns the PDF rendering of the agreement, and the .docx variant returns a Word version. Use these for archival downloads or when forwarding the executed document to a counterparty's records system.

### Can I limit what my agent is allowed to do with the Concord API?

Yes. Because you run Jentic One yourself, your own rules decide which Concord operations and credentials the agent may use. Concord puts the organization and agreement ids in the URL path, such as `/organizations/{organizationId}/agreements/{agreementUid}`, so a rule can pin the agent to a single organization or agreement. You also choose the exact operations it may call, so you can allow reading agreements and posting comments while withholding version uploads or signature routing until you grant them.