Skip to content
FingerTrackIDFingerTrackID Docs
Live in production, in shadow mode: FingerTrackID recommends, your system decides.Status →

Moving from v1 to v1.1

The v1.1 request is the v1 request with a tag in place of the fixed journey. The route, the HMAC signature, the headers, the 16384-byte limit, the references, the browser token and the retry rules do not change. This page lists what does.

Build and test the new body against the published v1.1 contract files: the v1.1 OpenAPI contract, its request and response schemas and the synthetic examples.

The body

Section titled “The body”
v1 v1.1
"schema_version": "event-assessment-request.v1" "schema_version": "event-assessment-request.v1.1"
journey, action and journey_context Removed. Sending any of them is 400 validation-failed
— tag, required: your name for the moment, at most ten digits in total (journeys and tags)
deadline_ms: the journey’s range deadline_ms: 250–5000, null = 5000, for every tag
Everything else Unchanged: external_event_id, idempotency_key, occurred_at, subject_ref, account_ref, event_context_token

The response

Section titled “The response”

The response of a v1.1 request is event-assessment.v1.1. It is the v1 response with tag in place of journey: the same status, score, recommendation, indicators, versions and size limit. Check that external_event_id and tag are the ones you sent, as you checked journey before. A v1 request still receives event-assessment.v1.

Steps

Section titled “Steps”
  1. Pick one tag per call site. For a login-only integration, login is enough. See the journey templates for other moments.
  2. Build the v1.1 body: change schema_version, drop journey, action and journey_context, add tag. Keep serializing once and signing the exact bytes you send.
  3. Use new external_event_id and idempotency_key values for v1.1 operations. An ID already used by a v1 operation, sent again as v1.1, is 409 idempotency-conflict: it is another operation, even for the same event.
  4. During a retry, never switch profiles. A v1 operation is retried as v1, with the same bytes.
  5. Read the response by its schema_version: event-assessment.v1 has journey, event-assessment.v1.1 has tag.
  6. On the console, the accesses of a v1.1 call show the tag; the earlier v1 accesses keep their journey name.

What does not change: the score, the policy and the recommendation for the same evidence; your credential and its permissions; the Web SDK; the feedback routes, which still address the assessment_id.

A v1 LOGIN call, as a v1.1 body:

{
  "schema_version": "event-assessment-request.v1.1",
  "external_event_id": "evt_login_0001",
  "idempotency_key": "idem_evt_login_0001",
  "occurred_at": "2026-11-03T14:05:22.481Z",
  "subject_ref": "usr_5c0e",
  "account_ref": null,
  "event_context_token": "ect_login_0001",
  "tag": "login",
  "deadline_ms": null
}