Working with Constrained Application Protocol

Start Developing Today
Working with CoAP allows you to access raw device data streams and develop your own applications and interfaces for working with your network.

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.

We highly recommend you read that you get familiar with CoAP and Silver Spring's implementation of the protocol by reading the CoAP Overview.


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)

The CoAP Gateway functions as a standard CoAP-to-CoAP proxy and its usage primarily follows the CoAP standard. Therefore, it can be implemented with standard tools, such as the libcoap library.

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.