# CoAP API Reference

The CoAP API is basically the same as the HTTP API, with certain adjustments due to constraining restrictions enforced by the CoAP protocol. The API requires the use of CoAPS, as content such as the JWT and AT must not be transported over an insecure connection.&#x20;

The current version of the API **only supports JSON** as the content format. However, we plan to support also **CBOR** as the content format in the future.&#x20;

The CoAP API has been designed considering the new [IETF draft](https://datatracker.ietf.org/doc/draft-ietf-ace-oauth-authz/) that attempts to define an OAuth 2.0 standard for CoAP. However, our solution goes beyond the new IETF draft by relying on additional best practices for Web for API security.

## Token API

The token API is for requesting access tokens issued by our IoT identity provider.

{% content-ref url="coap-api-reference/token-api" %}
[token-api](coap-api-reference/token-api)
{% endcontent-ref %}

## IdP API

The IdP API is used to validate issued access tokens with our IoT identity provider.

{% content-ref url="coap-api-reference/idp-api" %}
[idp-api](coap-api-reference/idp-api)
{% endcontent-ref %}

## Device API

The device API is used for updating device information registered with our IoT identity provider.

{% content-ref url="coap-api-reference/device-api" %}
[device-api](coap-api-reference/device-api)
{% endcontent-ref %}

