Doc Concordnow Concord

Name: Concord API
Brand: Concord
Availability: InStock

✓ Official Vendor SpecStorageDocument ManagementapiKey117 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Concord to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Concord, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Concord API.

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

GET STARTED

Start building with Concord API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Concord API for, with concrete tasks.

★ 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.

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.

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.

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.

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

Key Endpoints

117 endpoints — concord is a contract lifecycle management platform that exposes 117 rest endpoints for working with agreements, signatures, templates and organisation structure.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Concord API through Jentic.

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.