API Reference
This API Reference provides comprehensive documentation for the Concord eVault REST API, enabling integration partners and organizations to programmatically interact with Concord eVault's secure document management capabilities. Version 1.0 — January 2026.
About Concord eVault
Concord eVault is a secure electronic document management and eVault system designed for organizations that need to store, manage, and transfer authoritative copies of electronic records. Concord eVault provides compliance with ESIGN, UETA, and industry-specific regulations for electronic document management.
Intended audience
This documentation is designed for integration partners building connections between their systems and Concord eVault, software developers implementing automated document workflows, system architects designing integration solutions, and technical operations teams maintaining API integrations.
Prerequisites
To use the Concord eVault API, you need a Concord eVault organization account, Access Key credentials with appropriate scopes, an HTTPS client capable of making REST API calls, and familiarity with the JSON data format.
Table of contents
| Section | Description |
|---|---|
| Authentication | Access Key authentication, scopes, and security |
| Packages API | Managing document packages in vaults |
| Draft Packages API | Creating and publishing draft packages |
| Folders API | Organizing packages in folder hierarchies |
| Workflows API | Grouping packages into workflows |
| Certified Prints API | Generating certified document prints |
| Vault Fields API | Managing custom metadata fields |
| Webhooks | Real-time event notifications |
| Package Releases API | Requesting, exporting, and acknowledging releases |
| Appendix | Reference tables, error codes, glossary |
Quick Start
- Obtain an Access Key. Contact your Organization Administrator to create an Access Key with the scopes you need.
- Configure authentication. Include your Access Key in the
Authorizationheader of every request using the Bearer token format. - Explore the API. Review the endpoint documentation for each API section to understand available operations.
Base URL
All API endpoints are relative to your Concord eVault instance:
https://evault.concordapps.com/api
Authentication overview
All API requests require authentication via Access Keys:
Authorization: Bearer vv_live_your_access_key_here
Access Keys are vault-scoped (each key is tied to a specific vault), permission-based (keys have specific scopes controlling access), auditable (all activity is logged with the Access Key identifier), and rate-limited (subject to request rate limits).
Available API scopes
| Scope | Description |
|---|---|
packages | Full access to packages |
packages:read | Read-only access to packages |
packages:write | Write access to packages |
draft-packages | Full access to draft packages |
draft-packages:read | Read-only access to draft packages |
draft-packages:write | Write access to draft packages |
folders | Full access to folders |
folders:read | Read-only access to folders |
folders:write | Write access to folders |
workflows | Full access to workflows |
workflows:read | Read-only access to workflows |
workflows:write | Write access to workflows |
certified-prints | Full access to certified prints |
certified-prints:read | Read-only access to certified prints |
certified-prints:write | Write access to certified prints |
vault-fields | Full access to vault fields |
vault-fields:read | Read-only access to vault fields |
Rate limits
| Limit | Value |
|---|---|
| Requests per minute | 120 |
| Requests per hour | 5,000 |
Rate limits are applied per Access Key.
Support & contact
Technical Support
For API issues, bugs, or technical questions, email support@concordfinance.com. Include request details, the response, and the traceId from any errors.
Account Management
For Access Key requests, scope changes, or account questions, contact your assigned account representative.
Documentation Feedback
To report documentation errors or request improvements, contact your account representative.
Legal notice
Confidentiality
This API documentation is provided to authorized Concord eVault customers and integration partners. The information contained herein is confidential and proprietary to Concord eVault.
Terms of Use
Use of the Concord eVault API is subject to your organization's Concord eVault service agreement, the Concord eVault API Terms of Service, and applicable data protection and privacy regulations.
Compliance
Concord eVault is designed to support compliance with the ESIGN Act (Electronic Signatures in Global and National Commerce Act), UETA (Uniform Electronic Transactions Act), and industry-specific electronic record regulations. Customers are responsible for ensuring their use of the API complies with applicable laws and regulations.
Limitation of Liability
While Concord eVault strives to ensure the accuracy of this documentation, it is provided “as is” without warranty. Concord eVault reserves the right to modify the API and documentation at any time.
Document Information
Title: Concord eVault API Reference. Version: 1.0. Last Updated: January 2026. Status: Production.
Revision History
Version 1.0 (January 2026) — Initial release.
Copyright © 2026 Concord eVault. All rights reserved.
