Heartbeat

nutrab2b.control.heartbeat.v2 · Control

Purpose: Liveness and last-sequence exchange so partners can detect gaps and request replay.
When to send: Every 5 minutes on idle connections.
Sender → receiver: Any → Any
Expected responses: none
Equivalent standards: -
Scenarios using it: -

Fields and mappings

Field	Type	Req	Description
at	datetime	yes	Time
last_sequences	array<object>		Last sequence sent per subject
subject	string	yes	Subject
sequence	integer	yes	Sequence

Business rules

None beyond schema and code lists.

Example

{
  "specversion": "2.0",
  "id": "evt-heartbeat-HEARTBEAT-1",
  "type": "nutrab2b.control.heartbeat.v2",
  "source": "urn:gln:0614141000012:erp",
  "subject": "HEARTBEAT",
  "time": "2026-11-02T09:00:00Z",
  "datacontenttype": "application/json",
  "dataschema": "https://nutrab2b.org/schemas/2.0/HEARTBEAT.json",
  "sender": {
    "gln": "0614141000012"
  },
  "receiver": {
    "gln": "4012345000009"
  },
  "correlationid": "CONV-RFQ-1001",
  "idempotencykey": "HEARTBEAT:HEARTBEAT:1",
  "sequence": 1,
  "env": "test",
  "data": {
    "at": "2026-10-31T09:05:00Z",
    "last_sequences": [
      {
        "subject": "PO-55012",
        "sequence": 3
      }
    ]
  }
}

Mapping checklist

Every required field populated from your system of record
Coded fields mapped to the Bodylia OpenB2B code lists
GLN, GTIN and SSCC check digits validated
Rules above pass in the validator
Idempotency key and per-subject sequence generated
Expected responses, including rejections, handled