TEST - Appendix C: ENGAGE™ Persistent Connection API - TEST

The ENGAGE Gateway implements a general 30 second timeout for all commands below; it is suggested that Alliance Partners use a similar value when implementing a timeout on Gateway responses. In particular, the /edgeDevices/{linkId}/database resource can take many seconds to complete for large databases which must be first transferred and then queued by the Gateway before a response is returned to the initiating client.

Due to the Gateway’s webserver implementation, extraneous forward slashes (/) used in endpoint URLs shown below are ignored; while this would be a non-standard use case in a machine-to-machine developed solution, it is noted herein for clarity’s sake. The reader-controller shares many of the same resources as the Gateway. The key difference being that the reader-controller is not linked to any other edge devices. As a result, the reader-controller will utilize the /edgeDevices/{linkId}/ resources, but the linkId will always be dev00000.