Concord

Concord is a contract lifecycle management (CLM) platform that combines contract creation, real-time negotiation and redlining, unlimited e-signature, and post-execution tracking in a single workflow. The Nexla connector communicates with the ConcordNow REST API, enabling you to read and write agreements, organizations, folders, tags, members, reports, and attachments programmatically.

Power end-to-end data operations for your Concord API with Nexla. Our bi-directional Concord connector is purpose-built for Concord, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Concord or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Concord workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

The Concord connector authenticates to the ConcordNow REST API using an API key that is passed in the X-API-KEY request header. Before creating a credential in Nexla, you must generate an API key in your Concord account and identify the subdomain associated with your organization.

Obtain a Concord API Key

API keys in Concord are generated from your account's integrations settings. Generating a key requires administrator privileges on the organization.

1. Sign in to your Concord account at https://secure.concordnow.com (or your organization's dedicated environment URL).

2. Click your account avatar or organization name, and open Automations (or Settings, depending on your plan).

3. Navigate to Integrations > Concord API.

4. Click Generate New Key to create a new API key.

5. Copy the generated key immediately and store it in a secure location.

   Important

   The full API key value is typically displayed only once at the time of creation. Copy and store it securely before leaving the page, as you may not be able to view it again afterward.

API access and key generation are available on Concord plans that include API and integration features. For complete details on API availability, key management, and rotation, refer to the Getting Started with the Concord API guide and the Concord API reference.

Identify Your Subdomain

The ConcordNow REST API is reached at a host that includes your account's subdomain—for example, an account at mycompany.concordnow.com uses the subdomain mycompany. Nexla constructs every API request URL using this subdomain, so it must match the environment where your data resides.

• To find your subdomain, sign in to Concord and inspect the host portion of the URL in your browser's address bar. The text that appears before .concordnow.com is your subdomain.

Use the subdomain that corresponds to the environment you intend to connect to. Production and sandbox (UAT) environments use different hosts, so verify that the subdomain matches the account holding the agreements and data you want to access.

Authenticate

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Concord API key in the API Key Value field. This is the secret token generated in your Concord integrations settings, and it is passed in the X-API-KEY header of each request. This value is stored securely and should be kept confidential.

4. Enter your account subdomain in the Subdomain / Environment field—for example, enter mycompany for an account at mycompany.concordnow.com. This value is required for all API endpoint URLs.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Concord connector tile, then select the credential that will be used to connect to the Concord instance, and click Next; or, create a new Concord credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Concord endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Most Concord endpoints are scoped to an organization, so they require an Organization ID. You can obtain your organization IDs using the List User Organizations endpoint, which returns every organization the authenticated user belongs to.

List User Organizations

This endpoint returns the list of organizations that the authenticated user is a member of. Use it first to discover the Organization IDs required by most other Concord endpoints.

• This endpoint requires no additional parameters. Select the template and the source is ready to test.
• Nexla reads each organization from the organizations array in the response, producing one record per organization.

The Organization ID values returned by this endpoint are used to configure organization-scoped endpoints such as List Agreements, List Folders, and List Reports.

Get Organization

This endpoint returns the details of a single organization. Use it when you need configuration or metadata for one specific organization.

• Enter the ID of the organization to retrieve in the Organization ID field. You can obtain this value from the List User Organizations endpoint.

List Agreements

This endpoint returns the agreements that belong to an organization. Use it to sync your contract portfolio—including status, parties, and metadata—into Nexla for reporting or downstream processing.

• Enter the ID of the organization whose agreements you want to ingest in the Organization ID field.
• This endpoint is paginated. Nexla automatically advances through pages using the start and limit parameters and stops when no further records are returned, so you do not need to configure pagination manually.

Each element of the returned array is treated as a separate record. To retrieve the full details of an individual agreement, use the Get Agreement endpoint with the corresponding agreement ID.

Get Agreement

This endpoint returns the full details of a single agreement by ID. Use it to retrieve complete agreement metadata, fields, and status for a specific contract.

• Enter the ID of the organization the agreement belongs to in the Organization ID field.
• Enter the ID of the agreement to retrieve in the Agreement ID field. Agreement IDs can be obtained from the List Agreements endpoint.

List Agreement Attachments

This endpoint returns the list of attachments associated with a specific agreement, such as exhibits, schedules, and supporting documents.

• Enter the ID of the organization the agreement belongs to in the Organization ID field.
• Enter the ID of the agreement whose attachments you want to list in the Agreement ID field.

This endpoint returns attachment metadata. To retrieve the binary content of an individual attachment, use the Download Agreement Attachment endpoint.

Download Agreement Attachment

This endpoint retrieves the content of a single agreement attachment by ID. Use it to ingest the actual document associated with an agreement.

• Enter the ID of the organization the agreement belongs to in the Organization ID field.
• Enter the ID of the agreement the attachment belongs to in the Agreement ID field.
• Enter the ID of the attachment to download in the Attachment ID field. Attachment IDs can be obtained from the List Agreement Attachments endpoint.

List Folders

This endpoint returns the list of folders in an organization. Use it to map the folder structure your agreements are organized into.

• Enter the ID of the organization whose folders you want to retrieve in the Organization ID field.

List Organization Members

This endpoint returns the list of members in an organization, including their roles. Use it to sync user and access data for governance or reporting.

• Enter the ID of the organization whose members you want to retrieve in the Organization ID field.
• This endpoint is paginated. Nexla automatically advances through results using the start offset and limit parameters and stops when no further records are returned.

List Reports

This endpoint returns the reports configured for an organization. Use it to discover available reports and their identifiers.

• Enter the ID of the organization whose reports you want to retrieve in the Organization ID field.
• This endpoint is paginated. Nexla automatically advances through pages using the page and numberOfItemsByPage parameters and stops when no further records are returned.

Records are read from the reports array in the response. To retrieve a single report's full details, use the Get Report endpoint with the corresponding report ID.

Get Report

This endpoint returns the details of a single report by ID for an organization.

• Enter the ID of the organization the report belongs to in the Organization ID field.
• Enter the ID of the report to retrieve in the Report ID field. Report IDs can be obtained from the List Reports endpoint.

List Tags

This endpoint returns the list of tags available in the system. Tags are used to categorize and organize agreements within Concord.

• This endpoint requires no additional parameters. Select the template and the source is ready to test.
• Records are read from the tags array in the response.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Concord data sources can also be manually configured to ingest data from any valid ConcordNow API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

ConcordNow endpoints follow the pattern https://{subdomain}.concordnow.com/api/rest/1/...—for example, https://mycompany.concordnow.com/api/rest/1/organizations/{organization_id}/agreements. Concord read operations use GET.

Concord list responses vary in shape: the List Agreements endpoint returns a top-level array (path $[*]), while List Reports nests records under a reports property ($.reports[*]) and List Tags nests records under a tags property ($.tags[*]). The X-API-KEY authentication header is handled automatically by Nexla based on your credential configuration and does not need to be added as a request header.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Concord data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Concord destination, and select the Send to Destination option from the menu. Select the Concord connector from the list of available destination connectors, then select the credential that will be used to connect to the Concord organization, and click Next; or, create a new Concord credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Concord endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Each destination template sends the Nexset record as a JSON request body to the corresponding ConcordNow API endpoint. Organization-scoped templates require an Organization ID, which you can obtain using the List User Organizations source endpoint. For templates that act on an existing agreement, member, or tag, the relevant ID field defaults to the {{id}} field from the incoming record—map your data so this field holds the correct identifier, or override it with an explicit value.

Create Agreement

This endpoint creates a new agreement within an organization. Each Nexset record is sent as the JSON agreement payload using an HTTP POST request.

• Enter the ID of the organization to create the agreement under in the Organization ID field.
• Ensure each Nexset record contains the agreement fields expected by the ConcordNow API, such as the title and template or document content.

For the complete agreement payload schema, refer to the Concord API reference.

Update Agreement

This endpoint updates an existing agreement—including its metadata, status, and fields—using an HTTP PUT request. Send the partial or full agreement payload as JSON.

• Enter the ID of the organization the agreement belongs to in the Organization ID field.
• Enter the ID of the agreement to update in the Agreement ID field. This field defaults to the {{id}} value from the incoming record.

Delete Agreement

This endpoint deletes (voids) an existing agreement using an HTTP DELETE request.

• Enter the ID of the organization the agreement belongs to in the Organization ID field.
• Enter the ID of the agreement to delete in the Agreement ID field. This field defaults to the {{id}} value from the incoming record.

Deleting an agreement is irreversible. Verify that the agreement IDs in your Nexset are correct before activating this destination.

Send Agreement for Signature

This endpoint sends an existing agreement for e-signature by creating a signature request. Send the signer details and signing options as the JSON payload.

• Enter the ID of the organization the agreement belongs to in the Organization ID field.
• Enter the ID of the agreement to send for e-signature in the Agreement ID field. This field defaults to the {{id}} value from the incoming record.
• Ensure each record contains the signer details and signing options expected by the ConcordNow signature-requests endpoint.

Apply Tag to Agreement

This endpoint applies one or more tags to an existing agreement using an HTTP POST request. Send the tag payload as JSON.

• Enter the ID of the organization the agreement belongs to in the Organization ID field.
• Enter the ID of the agreement to apply the tag to in the Agreement ID field. This field defaults to the {{id}} value from the incoming record.

Tag IDs can be obtained using the List Tags source endpoint, or created using the Create Tag destination endpoint.

Remove Tag from Agreement

This endpoint removes a previously applied tag from an agreement using an HTTP DELETE request.

• Enter the ID of the organization the agreement belongs to in the Organization ID field.
• Enter the ID of the agreement the tag is applied to in the Agreement ID field.
• Enter the ID of the tag to remove in the Tag ID field. This field defaults to the {{id}} value from the incoming record.

Upload Agreement Attachment

This endpoint uploads a new attachment—such as an exhibit, schedule, or supporting document—to an existing agreement. Send the attachment payload as JSON.

• Enter the ID of the organization the agreement belongs to in the Organization ID field.
• Enter the ID of the agreement to upload the attachment to in the Agreement ID field. This field defaults to the {{id}} value from the incoming record.

Create Folder

This endpoint creates a new folder within an organization using an HTTP POST request. Send the folder payload (name, parent, and other properties) as JSON.

• Enter the ID of the organization to create the folder under in the Organization ID field.
• Ensure each Nexset record contains the folder name and any other properties expected by the ConcordNow folders endpoint.

Create Tag

This endpoint creates a new tag in the system using an HTTP POST request. Send the tag payload (name, color, and other properties) as JSON.

• This endpoint requires no path parameters. Ensure each Nexset record contains the tag properties expected by the ConcordNow tags endpoint.

Add Organization Member

This endpoint invites or adds a new member to an organization using an HTTP POST request. Send the member payload (email, role, and other properties) as JSON.

• Enter the ID of the organization to add the member to in the Organization ID field.
• Ensure each Nexset record contains the member email, role, and any other properties expected by the ConcordNow members endpoint.

Remove Organization Member

This endpoint removes a member from an organization using an HTTP DELETE request.

• Enter the ID of the organization the member belongs to in the Organization ID field.
• Enter the ID of the member to remove in the Member ID field. This field defaults to the {{id}} value from the incoming record.

Manual configuration

Concord destinations can also be manually configured to send data to any valid ConcordNow API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Concord write operations use POST to create resources, PUT to update agreements, and DELETE to remove agreements, members, or tags. ConcordNow endpoints follow the pattern https://{subdomain}.concordnow.com/api/rest/1/...—for example, https://mycompany.concordnow.com/api/rest/1/organizations/{organization_id}/agreements. For update or delete operations, include the ID of the object to be modified at the end of the URL path.

The ConcordNow API expects JSON for all write operations. The X-API-KEY authentication header is handled automatically by Nexla based on your credential configuration and does not need to be added as a request header.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to Concord, open the destination resource menu, and select Activate.

The Nexset data will not be sent to Concord until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.