BUSINESS CASES
Where this module fits
- device-bound encrypted messaging
- security alerts
- workflow reminders
- owner-scoped attention queues
- notification acknowledgement and archival
Operate · API module
Notifications
Bootstrap a cryptographically bound messaging identity and expose an owner-scoped account-signal inbox without making delivery, acknowledgement, or presentation metadata authoritative for business state.
PRIMARY CONSUMERS
Who integrates it
- account applications
- support systems
- alerting agents
- secure messaging clients
PREREQUISITES
What must exist first
- an authenticated Identity session with a stable device identifier for messaging bootstrap
- trust:write for device enrollment or trust:read for ticket issuance
- profile:read for inbox reads or profile:write for acknowledgement
- secure local custody of both messaging private keys
RECOMMENDED WORKFLOW
Compose the module safely.
- 01
generate independent Ed25519 signing and X25519 encryption keys on the device when secure transport is required
- 02
register public keys with an exact domain-separated proof of possession
- 03
obtain a short-lived session- and device-bound messaging ticket
- 04
list all or unread owner-scoped signals
- 05
re-read the referenced authoritative resource before acting
- 06
mark selected signals read, unread, or archived with an idempotent command
Endpoint reference
Explore this module’s endpoints.
Check each endpoint’s availability and required permissions. Planned routes and routes awaiting deployment are preparation references, not callable APIs.
GETMobile messaging device status
/api/v2/identity/messaging/device-status/{session_id}Return mobile messaging device status through the authoritative trust service boundary.›POSTRegister messaging device keys/api/v2/identity/mobile/messaging/deviceBind one authenticated application installation to independently generated Ed25519 signing and X25519 encryption public keys after proof of possession, then return a signed device credential.›GETIssue messaging ticket/api/v2/identity/mobile/messaging/ticketIssue a short-lived device- and session-bound messaging ticket for an installation with an active signed device credential.›GETList account signals/api/v2/notifications/allList the authenticated profile and workspace's cursor-paginated operational signals, including unread count and optional archived-history inclusion, without granting authority over any referenced domain action.›POSTMark account signals/api/v2/notifications/markAtomically set one to 100 owner-scoped notification records to UNREAD, READ, or ARCHIVED using an idempotent acknowledgement command.›POSTPush new notification/api/v2/notifications/pushPlanned capability: apply the requested transition to push new notification through the authoritative notification service boundary.›GETList unread account signals/api/v2/notifications/unreadList only unread operational signals for the authenticated profile and workspace, with the same bounded cursor and no-authority guarantees as the complete inbox.›