Developing with CoAP APIs
The most common use case for developing with CoAP is when you would like to make use of the raw network traffic and device data in order to develop your own custom applications or integrate directly to devices.
The CoAP Gateway is a UDP-based Constrained Application Protocol (CoAP) interface that exposes a forward proxy for Read/Write access to devices on the SSN mesh network. Users of this API and documentation are expected to be familiar with CoAP functionality.
In addition, here are links to the CoAP specifications:
- RFC 7252 - The Constrained Application Protocol (CoAP)
- RFC 7390 - Group Communication for the Constrained Application Protocol (CoAP)
- RFC 7641 - Observing Resources in the Constrained Application Protocol (CoAP)
- RFC 7650 - A Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD)
Note: You might find it somewhat problematic to use the Firefox Copper (CU) CoAP add-on for proxy operations because of the requirement to establish a session. However Copper can be used for CoAP access to the proxy itself.