.svg)
.svg)
Your registers and your systems, connected.
Credentially reads the registers you are accountable to, moves compliance data in and out of the systems you already run, and connects to anything else through a public API that anyone can build against.
All integrations
Most systems connect through the public API.
Read the API documentationThe Credentially connector
Coming soonIntegrations built around how you work.
Every organisation uses its systems differently, with its own tables, fields and values, so no two integrations are the same. The Credentially connector maps your fields and values through configuration, without a development project, so your own systems stay as they are.
Three ways to use it
On a schedule or as things happenKeep records in step
Bring staff in from your CRM or ATS and keep their details up to date. Changes made in Credentially go back, field by field, to systems that accept updates.
Connect systems through Credentially
Records from one system can carry the ID each person has in a second system. Credentially uses that ID to find the person's record there and passes the mapped details on. It can update existing records in the second system or create new ones.
Extend what your systems can do
Send people or documents to Credentially, let its automations and AI agents do the work, and get the results back in your own system.
The steps that read from and write to your systems run as configured automations, so what goes out is predictable. AI agents work on the data in between, once it is in Credentially.
How a connection is put together
Each system is configured once. Every organisation on it then connects with its own credentials and its own mapping.
The connector
One per system. It describes that system's API, including its addresses, sign-in method and operations, and is written as configuration and reviewed by Credentially engineering.
Reused across organisationsYour connection
Your organisation's own credentials for that system, stored encrypted and never shown again. On your side it is usually just access: credentials, and sometimes permissions or a webhook.
Set up by your admin or our teamThe sync
What moves and when: on a schedule, when something changes in Credentially, when your system sends a notification, or on demand. Admins map fields with a visual mapper.
Mapped to your fieldsTest first, then switch on
Before live writes begin, a test run shows what would change. They are switched on by Credentially staff, calls are recorded for audit, and a connection can only reach the addresses it has been approved for.
To add a system that has no connector yet, once its API and sign-in method are settled.
Including API keys, username and password, OAuth, signed requests and certificates.
Files come in as Credentially documents with their type, issue date and expiry date.
Build on Credentially
Built to be connected to.
The integrations named above are the ones we have built and maintain. Anything else connects through the REST API. The documentation is public, with a downloadable specification, and Credentially issues a key on request.
Read the API documentationKeys issued by Credentially
Request a key through support or your customer success manager. A key reaches all staff documents and data, so it is handled as a credential.
Bearer token authorisation
Every request carries the key as a bearer token. The word Bearer goes in front of the key itself.
Gateways in three regions
A gateway and a webhook gateway in the UK and Europe, the United States and Canada, each on its own base URL.
A UAT environment first
A UAT environment with its own gateway and webhook gateway. The documentation publishes one for Europe only.