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

# Doc Concordnow Concord

Concord is a contract lifecycle management platform that exposes 117 REST endpoints for working with agreements, signatures, templates and organisation structure. The API covers agreement creation and metadata, e-signature flows, automated templates, webhooks for lifecycle events, user and organisation administration. Authenticated via X-API-KEY, it suits CLM integrations, sales-ops automation and audit/reporting pipelines that need to keep contract data in step with downstream systems.

## For AI agents

Create, send and track contracts and e-signatures in Concord, plus subscribe to lifecycle webhooks and manage templates and organisation users.

## Scope

Does not handle billing, payment collection, document scanning OCR, or generic file storage - use for contract lifecycle and e-signature workflows only.

## Capabilities

- Create agreements from scratch or from an automated template
- List and filter agreements by folder, status or organisation
- Pull agreement metadata, summaries and end-clause data for analytics
- Send agreements for signature and track signature status
- Subscribe to webhooks for agreement, signature and lifecycle events
- Manage organisation members, invitations and roles
- Read structured contract data including parties, dates and signed labels

## Use cases

### Sales-Ops CLM Integration

Push closed-won deals from a CRM into Concord by calling /organizations/{organizationId}/agreements to create the contract from a template and populate counterparty fields. Then poll or subscribe to webhooks to update the CRM when the contract is signed. Removes manual contract drafting and keeps deal records accurate.

Example prompt: POST /organizations/{organizationId}/agreements with a templateId and party metadata for a closed-won deal, then watch for the agreement.signed webhook.

### Contract Analytics and Reporting

Build a contract analytics dashboard by pulling /summary endpoints for each agreement, including lifecycle stage, end clauses and signed labels. This lets legal and finance teams answer questions like 'how many MSAs auto-renew next quarter?' without manually opening every contract. The 117-endpoint surface is broad enough to power a full CLM analytics layer.

Example prompt: GET /organizations/{organizationId}/agreements then for each, GET /agreements/{agreementUid}/summary/lifecycle and aggregate by stage.

### Automated Template Generation

Use Concord automated templates to standardise contract drafting. The API lets a workflow tool fill placeholder fields and generate a ready-to-send agreement in one call. This is especially useful for high-volume use cases like vendor agreements, employee NDAs or recurring service orders where consistency matters.

Example prompt: Call the automated template endpoint to generate a vendor NDA from template id with the counterparty name and effective date filled in.

### AI Agent Legal Operations Assistant

Through Jentic, an AI assistant for a legal-ops team can answer 'which contracts expire in the next 60 days?' or kick off an NDA from a Slack message. The agent searches Jentic for the relevant intent, loads the Concord operation, and executes against the org's API key. This collapses what would be a manual CLM lookup into a chat-driven workflow.

Example prompt: Use Jentic to search 'list Concord agreements', load /organizations/{organizationId}/agreements, and filter by upcoming end_date to flag renewals.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /organizations/{organizationId}/agreements | List agreements in an organisation |
| GET | /organizations/{organizationId}/agreements/{agreementUid}/summary | Get a contract summary |
| GET | /organizations/{organizationId}/agreements/{agreementUid}/metadata | Read structured agreement metadata |
| GET | /organizations/{organizationId}/agreements/{agreementUid}/summary/lifecycle | Get the lifecycle stage of an agreement |
| GET | /user/me/organizations/{organizationId}/agreements | List agreements visible to the current user |
| GET | /user/me/organizations/{organizationId}/folders | List folders the user can access |

## Key resources

- **Agreements** — Create, list, update and inspect contracts and their metadata
- **Signatures** — Send agreements for signature and track signer status
- **Automated Templates** — Generate agreements from reusable templates
- **Webhooks** — Subscribe to agreement and signature lifecycle events
- **Organizations** — Manage organisation members, invitations and folders
- **Users** — User profile, current-user and account access

## Why Jentic

- **Setup:** Wiring Concord by hand means carrying its X-API-KEY header and threading organization and agreement ids through contract lifecycle calls yourself. Through Jentic you install once, import the Concord API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Concord puts the organization id in the URL path (/organizations/{organizationId}/agreements), so a rule can pin your agent to one organization: it can list and read that organization's agreements and nothing else. You choose the operations it may call, so reading a specific agreement's lifecycle is not included unless you add it.
- **Credential handling:** Your Concord X-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 'list contracts' or 'read an agreement summary', 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

- **Docassemble API** — Open-source document assembly platform that produces contracts via guided interviews instead of CLM templates
- **GitHub API** — Source-control API that pairs with Concord when contracts are stored as code-reviewed Markdown templates
- **Asana API** — Track contract review tasks alongside Concord documents.
- **Slack API** — Notify a Slack channel when a Concord document changes status.

## FAQ

### What authentication does the Concord API use?

Concord uses an API key supplied in the X-API-KEY header. Each organisation gets its own key. When called through Jentic, the key sits in your Jentic One instance and the agent receives a scoped reference, so the raw key never enters the model context.

### Can I create an agreement from a template with the Concord API?

Yes. Use the automated template endpoints under /organizations/{organizationId} to generate an agreement from a saved template, populating placeholder fields in a single call. This is the standard path for high-volume contract creation.

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

Concord does not publish public rate limits in the spec. Production integrations should handle 429 responses with exponential backoff and avoid pulling all agreements in a single request - page through /organizations/{organizationId}/agreements instead.

### How do I track when a contract is signed with the Concord API through Jentic?

Subscribe to a webhook on signature.completed via the Webhooks endpoints. Through Jentic, search 'subscribe to Concord webhook', load the operation and execute with your callback URL. Jentic stores the X-API-KEY so the agent can register webhooks without seeing the secret.

### Can I read structured contract metadata with the Concord API?

Yes. GET /organizations/{organizationId}/agreements/{agreementUid}/metadata returns the structured fields configured on the agreement, and the /summary endpoints return lifecycle, signed labels and end clauses for reporting.

### Is the Concord API free?

API access is included with paid Concord plans. Concord does not publish a separate API price; check current Concord pricing tiers for organisations and feature inclusions.

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

Yes. Because you self-host Jentic One, your own rules decide which Concord operations and credentials the agent may use. Since Concord puts the organization id in the URL path, such as /organizations/{organizationId}/agreements, you can pin the agent to a single organization and grant only the operations you want, for example listing and reading that organization's agreements. If you do not add the lifecycle summary or metadata endpoints, the agent cannot call them.