Skip to main content

​
Three different acknowledgments

  1. Protocol delivery: the SDK reports delivery of a message.
  2. Application acceptance: the receiving application validates and records the requested operation.
  3. Backend acceptance: the destination system commits the record according to its API contract.
Track these separately. message_delivered does not prove that a technician accepted a task or that a backend committed it.

​
Identity and permission

Verifying an address proves its relationship to a key. Your application decides which key may access a record or perform an operation. Bind approved addresses to your own users, devices or roles during enrollment.

​
Local and hosted operation

A local path can remain available when internet access is lost. A partition between peers is different: work stays local until a path returns, subject to retention and expiry. Hosted identity, relay and telemetry each have their own credentials and connectivity requirements. The receiving core acknowledges before message_received and never persists inbound content. Install a durable receiving handler before start(); a delivery event alone does not establish that the app stored the record.