CONSEN

Product

Solutions

Resources

Pricing

For developers

Application processes as data, with an API and webhooks around them

Every form, workflow and offering in CONSEN is a JSON definition. Workspace API keys read applications and send invitations, and signed webhooks tell your systems when something changes.

JSON definitions

Your whole process is data, not code

Forms, applications, workflows and offerings are structured definitions. Rules, calculations and conditional documents are data the engine reads, never code it runs, and each application keeps the definition it started with. The visual designer works on the same definitions.

Steps, branches, rules and scoring in one definition

Checked before publishing, so every outcome leads somewhere

Templates are definitions too, applied to your workspace

workflow definition (excerpt)
{
  "id": "docs",
  "type": "documentNode",
  "data": { "label": "Documents", "config": { "documents": [
    { "name": "Bank statements, last 3 months",
      "required": true, "maxAgeDays": 45 },
    { "name": "Articles of incorporation",
      "required": true,
      "when": { "field": "mortgage.borrower_type",
                "op": "==", "value": "Corporation" } }
  ] } }
},
{
  "id": "id_person",
  "type": "reviewNode",
  "data": { "label": "Identification",
            "config": { "record": ["identity", "file-note"] } }
}

API keys

Workspace API keys with only the access they need

Send the key as a bearer token to your workspace's API. Each key carries one or more scopes.

applications:read

List applications, filtered by status, offering, case reference or last update, and download each application's package.

reviews:read

Adds review decisions and the records your reviewers filled in to the packages.

invitations:write

Send invitations to an offering, with a case reference, and list their status.

Created and revoked by your workspace's administrators, in Settings › Integrations.

Shown once when created. CONSEN stores only a SHA-256 hash of the key.

A revoked key stops working within about 2 minutes.

Up to 1,000 requests an hour per key, and up to 10 active keys per workspace.

Every package download is in the access log, with the key's name.

A key reaches only the routes of its scopes. Settings and the admin API refuse keys.

The application package

Everything about one application, in one response

Reviewers, administrators and keys with applications:read can download an application's package. It never includes IP addresses, card digits or staff-only history, and an erased application answers 410 Gone.

Applicant name and email, status, case reference and offering

Answers with the forms' field titles, offering values and calculated values

Documents with their dates, as download links valid for 15 minutes

Consent records: version, time and text fingerprint

Signatures: who, when, document fingerprint and the signed PDF

Payments: amount, currency and reference, never card details

Provider check outcomes

With reviews:read: review decisions and review records

Webhooks

Signed webhooks when an application changes

Thin by design: the body says what happened and to which application, never the answers or personal data. Your system fetches the package with a key.

application.submittedapplication.changes_requestedapplication.approvedapplication.rejectedapplication.completedapplication.withdrawn
POST to your endpoint
{
  "id": "evt_…",
  "type": "application.submitted",
  "createdAt": "2026-11-16T15:00:00Z",
  "workspace": "acme",
  "data": {
    "applicationId": "…",
    "offering": "mortgage",
    "offeringName": "Private mortgage application",
    "status": "PENDING_REVIEW",
    "updatedAt": "…"
  }
}

Signed with HMAC-SHA256 and your webhook's secret, in the Consen-Signature header (t=<time>,v1=<signature>).

Retried after about 1, 2, 4, 8 and 16 hours until your endpoint answers with a 2xx: six tries in all.

The event id stays the same across retries, so you can ignore one you've already handled.

Every try is in a delivery log for 30 days, visible to your administrators.

HTTPS on port 443 to a public host name only, with no redirects; up to 5 webhooks per workspace.

Verify a webhook

Check the signature before you trust the body

Compute HMAC-SHA256 with the webhook's secret over the timestamp, a dot and the raw body, compare it in constant time with v1, and reject timestamps older than a few minutes.

verify.py
import hashlib, hmac, time

def verify(secret, header, body):
    # header: Consen-Signature, body: the raw request body
    parts = dict(p.split("=", 1) for p in header.split(","))
    expected = hmac.new(secret.encode(), f"{parts['t']}.{body}".encode(),
                        hashlib.sha256).hexdigest()
    return (hmac.compare_digest(expected, parts["v1"])
            and abs(time.time() - int(parts["t"])) < 300)
verify.js
const crypto = require("crypto");

function verify(secret, header, rawBody) {
  // header: Consen-Signature, rawBody: the raw request body
  const parts = Object.fromEntries(
    header.split(",").map((p) => p.split("=")));
  const expected = crypto.createHmac("sha256", secret)
    .update(`${parts.t}.${rawBody}`).digest("hex");
  const fresh = Math.abs(Date.now() / 1000 - Number(parts.t)) < 300;
  return fresh && expected.length === (parts.v1 || "").length &&
    crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(parts.v1));
}

What's available

Available today, and on request

Available today

JSON definitions

Forms, workflows and offerings as structured data.

Available today

Workspace API keys

Scoped, hashed, revocable.

Available today

Application package

Everything about one application, in one response.

Available today

Signed webhooks

Status changes with retries and a delivery log.

On request

API reference

Endpoints, filters and examples, shared with your team.

On request

Delivery into your systems

Answers and files sent straight to a CRM or loan system, built with you.

FAQ

Questions from developers

Not yet. We share the API reference and examples on request with the administrators and developers of a workspace. Contact us and tell us what you want to connect.

No. Workspace API keys only read applications, read review records and send invitations, depending on their scopes. Processes are built in the visual designer, which works on the same JSON definitions; building a process from a definition you supply is done with our team during onboarding.

On purpose. A webhook says what happened and to which application, never the answers or personal data. Your system then downloads the application's package with an API key, so personal data only moves over a request you authenticate.

Any 2xx response counts as delivered. Otherwise the delivery is retried after about 1, 2, 4, 8 and 16 hours, six tries in all. Every try is in the delivery log for 30 days, and each event keeps the same id across retries so you can ignore duplicates.

On request. Delivering answers and files directly into a specific system of yours is built with you during onboarding. Until then, a small service of yours can listen for webhooks and fetch each package.

Connect CONSEN to your systems

Tell us what you want to build. We will send the API documentation and help your team with the first key and webhook.