Getting started


Before you start

EADFactory is designed for developers, engineers, or anyone else who's comfortable creating custom-coded solutions or integrating with platforms. If you think you may need some help integrating with EADFactory do not hesitate to contact one of our experts.

In order to use any functionality of EADFactory, the first thing you need to do is to request access from our team. There is no self-service registration: please contact us and we will provide you with the credentials described in the next section.

Authorization

After you have successfully registered and you are logged in, you have to be authorized by our team to be able to use the API.
For that, you can request a client identifier and a client secret. We will provide you also a login URL for your client.

Login

Once you have received the client identifier and the client secret, you can request a token. Send the parameters in the request body, as application/x-www-form-urlencoded:

curl -X POST 'https://{login_url}' \
  -H 'Content-Type: application/x-www-form-urlencoded' \
  -d 'grant_type=client_credentials' \
  -d 'client_id={clientId}' \
  -d 'client_secret={clientSecret}'

Do not put the client secret in the query string. It works, but the secret then travels in the URL, where proxies, gateways and access logs record it in clear. Send it in the body.

scope=token is optional: your client is already configured with that scope, and the token comes back with it either way.

Access token

The response carries the token and its lifetime:

{"token_type":"Bearer","expires_in":3600,"scope":"token","access_token":"eyJ..."}

Pass it on every request as an authorization HTTP header:

Authorization: Bearer {access_token_here}

The Bearer prefix is not optional. Sending the raw token does not produce a 401: the gateway finds no matching route and answers 404. See Base-paths.

What the token contains

The token is a JWT and you can decode it without any secret. A couple of its claims decide whether a request will work, so it is worth looking at yours once:

Claim Example What it means
tenant acme Your tenant. The platform reads it from here, not from a header. There is no tenant header, and sending one has no effect.
aud https://{your-host} The host this credential is valid for. If you are unsure which base-path to use, this claim is the answer: it is the host, verbatim.
exp, iat A token lasts 3600 seconds. Cache it and reuse it; do not request one per call.

Why a credential that looks right can still fail

A credential is issued per environment and per manager. Neither restriction is visible in the credential itself, and each one fails in a different way:

What you did What comes back What it means
Correct host, enabled manager 200
A token issued for another environment 401, No credentials found for given 'iss' The token is valid, but not here. Check the aud claim.
A manager your tenant is not enabled for 400, #TENANT_IS_NOT_VALID# Not a mistake in your request. Ask us to enable that manager for your tenant.
A host where your tenant is not routed 404, no Route matched with those values The request never reached the service. Six causes, listed under Base-paths.

Access is granted per manager, not per platform. Being able to call Evidence Manager does not mean you can call Signature Manager: that is a separate activation, and until it is done you get #TENANT_IS_NOT_VALID# however correct your request is.

The API contracts

The four OpenAPI contracts are public and need no credentials, so you can download them and generate a client before your access is set up:

{host}/swagger/digital-trust-api-1.0.yml       Evidence Manager
{host}/swagger/notifications-api-1.0.yml      Notification Manager
{host}/swagger/chat-manager-bot-api-1.0.yml   Chat Manager
{host}/swagger/signature-manager-1.0.yml      Signature Manager

Each one is also browsable as a catalogue, and the links are in the sidebar of every page. The list of hosts is under Base-paths.

The interactive catalogue is served from production and from integration. On preproduction it does not answer: depending on the manager you get a 500, a 401 or a 404. That is how the gateway is set up there, not a problem with your credentials, and it does not say anything about the API itself being down in that environment.

If you are working against preproduction, download the contract instead and use your own client.

This is a server-to-server API. A browser cannot call it directly: the CORS preflight never carries the Authorization header, so the gateway answers 404 to it. Your credentials must stay on your backend.

Prefer to work from an AI assistant?

The same operations are available as tools for MCP-compatible assistants (Claude Desktop, Claude Code, Cursor…), with the same credentials and against the same hosts. See Use the API from an AI agent.