Merge365 integration: contracts, acknowledgements and retries
Separate a delivered request from a confirmed physical result.
Updated
Principle and limits
Define the source event, canonical identifier, timestamp, target and permitted action. A connector translates between application concepts and supported device behavior. Translation does not make every device expose the same capabilities. Validate the selected connector, firmware, network path, permissions and licensing before relying on a workflow. This guide defines acceptance questions, not an API endpoint specification.
Installation and acceptance
Test duplicate and delayed events, invalid permissions, disconnected devices and restored connections. Distinguish request accepted, connector delivered, device acknowledged and physical outcome verified. Check ordering assumptions, retry limits and failure visibility. Only the deployed API and connector documentation can confirm exact payloads, authentication and supported commands.