Can I manage rules through the API?

Rules and cases are managed in the dashboard today; the public API returns decisions and sends case.decided webhooks.

Who can see the record during review?

Only roles with the reveal permission, and each reveal is logged with the reviewer, case and time.

Workflow

Review queue and decision rules

Rules approve, reject, flag, notify or open a case on every settled verification, and each decision is written back and sent by webhook.

Create an account Read the docs

What it does

Review Queue & Rules, in detail.

Rules in JSON

Conditions over status, match, field_matches.*, summary.* and repeat.*, nested with all, any and not.

Built-in triggers

not_found, no_match, field mismatches, liveness_failed, face_mismatch, risk levels and watchlisted open cases without any rule.

A default rule set

Watchlisted subjects, high risk and inactive companies open cases; subjects checked three or more times in 30 days are flagged.

Decisions on the record

GET /v1/verifications/{id}/decision returns the outcome, who decided, and the case status, priority, reason codes and SLA.

Test before you enable

Run a rule against recent verifications in the dashboard to see what it would have done.

Exports and retention

PII-free CSV exports, retention from 30 to 3,650 days, and erasure with a tamper-evident record.

How it works

From request to decision.

1
Write a rule
In the dashboard, pick the product, conditions, action and priority.
2
Verifications are evaluated
Rules run after each verified or not_found result, then the built-in triggers.
3
Analysts decide
Cases show the assertion and signals, with an audited reveal; case.decided notifies your system.

Routing and providers

Rules and cases live in the dashboard and console API. The public API exposes each verification’s decision and the case.decided webhook.

Use it

One request. One normalized response.

Call GET /v1/verifications/spm_1d3e5b4251d97fc1c41073fa/decision through @speedmap/node, speedmap for Python.

Read the guide API reference

Request

curl http://localhost:4000/v1/verifications/spm_1d3e5b4251d97fc1c41073fa/decision \
  -H "Authorization: Bearer sk_test_..."

Response · 200 OK

{
  "object": "decision",
  "reference_id": "spm_1d3e5b4251d97fc1c41073fa",
  "outcome": "review",
  "by": null,
  "rule_id": null,
  "case_id": "case_189d18e3c5f90d30",
  "flags": [],
  "decided_at": "2026-10-20T12:55:34.800Z",
  "case": {
    "id": "case_189d18e3c5f90d30",
    "status": "open",
    "priority": "normal",
    "reason_codes": [
      "no_match",
      "field_mismatch:date_of_birth"
    ],
    "decided_at": null,
    "sla_due_at": "2026-10-21T12:55:34.800Z",
    "created_at": "2026-10-20T12:55:34.800Z"
  }
}

Use cases

Where Nigerian teams use it.

Lending

Auto-reject date-of-birth mismatches and send partial name matches to an analyst.

Payments and marketplaces

Open a case when a seller’s company is inactive or the account name does not match.

Account opening

Flag subjects seen repeatedly across the platform in the last 30 days.

Government and agencies

Four-eyes decisions with a complete, exportable audit trail.

Part of:Lending Government & agencies

What you get back

The fields you will read.

Field	Meaning
decision.outcome	approved, rejected, review, flagged, escalated or null
by / rule_id / case_id	rule, reviewer or null (the engine opened a case), and where
case.status / priority / reason_codes	open, in_review, approved, rejected or escalated; normal or high; the triggers that opened it
case.sla_due_at	When the case is due under your review SLA (24 hours by default)
webhook case.decided	Fired on every reviewer decision

decision.outcome
Meaning
approved, rejected, review, flagged, escalated or null
by / rule_id / case_id
Meaning
rule, reviewer or null (the engine opened a case), and where
case.status / priority / reason_codes
Meaning
open, in_review, approved, rejected or escalated; normal or high; the triggers that opened it
case.sla_due_at
Meaning
When the case is due under your review SLA (24 hours by default)
webhook case.decided
Meaning
Fired on every reviewer decision

Assertion tier

Cases show assertions and signals. A record reveal is a separate, audited action.

Full tier

Reviewers with the permission can reveal the sealed record inside the case.

Pricing

No extra fee: you pay for verifications, not cases, rules, exports or seats.

Documentation See pricing plans

FAQ

Review Queue & Rules questions.

Need more detail? Read the documentation or talk to our team.

Can I manage rules through the API?: Rules and cases are managed in the dashboard today; the public API returns decisions and sends case.decided webhooks.
Who can see the record during review?: Only roles with the reveal permission, and each reveal is logged with the reviewer, case and time.

Start verifying in minutes. Go live when you’re ready.

Create your account in under a minute and explore the full dashboard. We switch your workspace live after a short compliance review.

Create an account Read the quickstart