ENSign inTry the sandbox

Integrations

Your application starts the flow. Signing Flows carries it through.

Two ways in. The REST API works today for any system that can make an HTTP call. No-code automation, with recipes for the usual cases, is built and switched on when you ask. Available works today within the limits stated in its own line; some features need account configuration · On request built and ready for the operator to enable when requested · In roadmap not built yet; no delivery date.

Your application → Signing Flows
  1. POST/api/v1/documents200
  2. PATCH/api/v1/workflows/:id200
  3. POST/api/v1/workflows/:id/signers200
  4. POST/api/v1/workflows/:id/dispatch200
Available

REST API v1

Create circuits, upload documents, assign signers and read the evidence. Idempotent requests, scoped tokens, and signed webhooks: your system is told when each document moves, for example when a circuit completes.

API referenceAPI demo (needs a token)
On request

No-code automation

Recipes you run from your automation tool, following the document from a trigger to a result. Built; the operator switches it on for your account when you ask.

Request a demo
Recipes

Eight things a team usually wants to automate.

Each recipe names the trigger, the steps and the result. They run on the no-code path; the same can be done through the API.

On request

From a sales system to the signature

When a deal is won, the contract goes out to sign on its own, and for 24 hours a repeated notice does not send it twice.

  1. Your sales system marks a deal as won
  2. Signing Flows sends the contract from a template
  3. Your sales system gets the reference of the flow

On request

From a form to the agreement

Receive agreements from a web form without anyone on your team loading them by hand.

  1. Someone fills in a form with their name, email and a PDF
  2. Signing Flows sends the agreement to that person to sign

On request

File what was signed

Every signed document is filed in order, checked against what the delivery package promises, without doing it by hand.

  1. Signing Flows tells you a flow is completed
  2. Download the delivery package and check the signed PDF against it
  3. Save the signed PDF and the completion report in a folder

On request

Warn the team of a decline or an expiry

Find out right away when someone declines or a flow expires, without checking by hand.

  1. Signing Flows tells you someone declined, or a flow expired
  2. Look up which document and what happened
  3. Email the team

On request

Keep an eye on the quota

You do not run out of quota by surprise: the administrator gets a message when any quota reaches 80%, and nothing otherwise.

  1. Every day at 8:00
  2. Read the plan and what has been used in the period
  3. Is any quota at 80% or more?
  4. If so, email the administrator

On request

A request in a minute, on a live board

A citizen asks for a certificate from their phone and gets it signed, approved, with the platform seal and delivered in about a minute, while a projected board lights up every step with its time. Nothing but first names and request numbers on screen.

  1. A citizen fills in a request from their phone
  2. Signing Flows generates the certificate from the agency template and sends it: the citizen signs, the officer approves
  3. On completion it gets the platform seal and is delivered by email
  4. A projected board lights up each step with its time

On request

Mailbox with acknowledgement of receipt

Whoever writes to your mailbox knows at once that the message arrived, and every PDF they attach keeps a timestamp. A sender that cannot be verified gets no automatic reply.

  1. Someone writes to your organisation’s mailbox
  2. Is the sender verified by its domain? If not, it is held for review and nobody is answered
  3. Signing Flows timestamps each PDF attachment
  4. The sender gets an acknowledgement of receipt

On request

Archive it where you archive

When a workflow is completed, the signed file, the report and the evidence land in your own storage, in a folder per category, with a small manifest beside them. A file that does not match its checksum is never saved.

  1. A workflow is completed
  2. Signing Flows hands over the signed file, the report and the evidence, and the signed file is checked against its checksum
  3. Folder, name and metadata are set by category
  4. Saved in your S3-compatible bucket or WebDAV folder
Connectors

Identity, signing, timestamp, validation and preservation services.

Each connector carries one of the same three states. Your country decides which identity and signing services an installation can offer.

Signing

Remote service of a provider · generic CSC 2.0 · platform key (P12 or HSM) · software on the signer’s computer.

Identity

Identity service · OpenID Connect · email and password · one-time code by email or SMS · wallet verifier (OpenID4VP) · SAML 2.0.

Time, validation and preservation

Time-stamp authority (RFC 3161) · own validation engine · preservation (B-LTA, ETSI TS 119 512) · trust lists.

Every connector and its current state →

maqueta SITIO-2 v7