Iotwerk
register bcd digit audit
Return decimal BCD values and illegal digit-nibble witnesses in supplied register byte strings. Supplied bytes only; no device connection or command.
POST https://iot.halowerk.com/v1/register-bcd-digit-auditInputs
| Field | Type | Required | Description |
|---|---|---|---|
| records | array | Yes | |
| signed_last_nibble | boolean | Yes |
Show full input schema
{
"type": "object",
"properties": {
"records": {
"type": "array",
"items": {
"type": "string",
"pattern": "^(?:[0-9a-fA-F]{2}){1,4096}$"
},
"maxItems": 100,
"minItems": 1
},
"signed_last_nibble": {
"type": "boolean"
}
},
"required": [
"records",
"signed_last_nibble"
],
"additionalProperties": false
}Published input example
{
"records": [
"1234",
"9a01",
"012c"
],
"signed_last_nibble": true
}Result & documentation
Machine-readable documentation of this hub
Source of this page: the published HALOWERK catalog. Updated: 2026-11-18 UTC.
More endpoints in this hub
- Iotwerk0.003 USDC
battery degradation
POSThttps://iot.halowerk.com/v1/battery-degradationApplies a transparent heuristic: cycle fade scales with equivalent full cycles and depth-of-discharge exponent; calendar fade scales with square-root time and a temperature factor. Coefficients are caller supplied or declared defaults. This
- Iotwerk0.002 USDC
device auth
POSThttps://iot.halowerk.com/v1/device-authCanonicalizes device_id, nonce and message, computes an HMAC-SHA256 tag with caller-supplied ephemeral key material, and optionally compares a claimed tag in constant time. It does not provision devices, store keys or replace asymmetric dev
- Iotwerk0.004 USDC
digital twin sync
POSThttps://iot.halowerk.com/v1/digital-twin-syncGroups caller-supplied scalar field changes by field name, selects the highest version, and reports a conflict when equal-version values differ. It does not connect to a twin platform, merge nested documents or resolve semantic conflicts.