API & Integrations

Accordia is designed to adapt to your systems, not replace them. If your organization already runs its work through an ERP, a CRM, or a document management system, you don’t have to move that work into Accordia to get certified evidence out of it.

With Accordia’s REST API, certification and traceability become a step inside your existing processes: your own system triggers the certified communication, the signature request, or the file exchange, and the evidence accumulates on the Case exactly as it would if you’d done it by hand in the app.

What is an API?

API stands for Application Programming Interface: a set of rules, protocols, and specifications that let different applications talk to each other and exchange data securely.

A REST API in particular is the common web standard for this — your system sends ordinary HTTP requests to Accordia and gets structured responses back. Any modern development stack can call one.

Typical integrations

• ERP — issue a certified communication automatically when an invoice falls overdue.
• CRM — send a contract for signature the moment a deal is marked as won.
• Document management system — certify the exchange and preservation of files as they’re archived, producing a hash, metadata, and a timestamp.

In each of these, your users keep working in the tool they already know.

API keys

Access is authenticated with API keys, generated and managed from your organization’s settings. Treat a key like a password: it acts on behalf of your organization, and anything done with it consumes your organization’s credits in the same way as work done in the app.

Only Organization Admins can manage API keys — see Users & Organizations.

Getting the technical documentation

The endpoint reference, authentication details, and request/response formats are maintained separately from this wiki. Contact the Accordia team at info@accordia.com to get access for your development team.