Skip to main content


This section introduces the nRF Cloud REST API.

REST stands for representational state transfer. It builds and exposes APIs for applications that communicate over the Internet.

If you are not familiar with REST APIs, start with the Postman Learning Center.

The nRF Cloud REST API

The nRF Cloud REST API is built on the OpenAPI 3.x specification. You can get the current schema as a JSON file in one of the following ways:

REST tools, such as Postman or Insomnia, can parse the downloaded file and create a collection of endpoints for you.

See also Using the REST API.


The REST API authenticates users with an API key (simple token), and devices with a JSON Web Token (JWT). Only a subset of the nRF Cloud REST API endpoints should be called by devices instead of users. These endpoints indicate JSON Web Token in the Authorizations section. Otherwise, Simple Token is indicated.

Some endpoints, like FetchCurrentPendingFOTAJobExecution, support both schemes.

API key (simple token)

Most requests to the REST API require a simple authentication token (API key) in the Authorization header. Here is a cURL example of this header:

-H "Authorization: Bearer d8be845e816e45d4a9529a6cfcd459c88e3c22b5"

You can retrieve and manage API keys through your User Account page on the nRF Cloud portal. Previously issued API keys are valid for up to 60 minutes.

JSON Web Token

REST endpoints intended for devices or proxy servers require a JWT. If you are not familiar with JWTs, learn more and create a JWT to use when calling the nRF Cloud REST API at, which also provides an Introduction to JWTs.

Devices using the REST API must also use modem firmware v1.3.x, which has its own hardware requirements as described in the release notes.


You cannot update to modem firmware v1.3.x from any previous version using the nRF Cloud firmware over-the-air (FOTA) service.

Signing (private) and verification (public) keys

JWTs must be signed by the private key of an ES256 asymmetric key pair. The only JWT algorithm nRF Cloud supports is ES256.


The nRF9160 DK and Thingy:91 are shipped with RSA256 certificates, which are not supported for JWT signing by modem firmware v1.3.x and later. To use JWTs with these devices, delete the device from nRF Cloud and re-provision it with a new ES256 device certificate.

When a JWT is received by an nRF Cloud endpoint, its digital signature must be verified by the corresponding public key.

nRF Cloud supports two types of private keys:

  • Device key: generated on the device and unique for each device.
  • Service key: generated by nRF Cloud and unique for each service, such as Location Services or the FOTA service. This is typically only used for proxy servers. Use of service keys requires a Pro or Enterprise plan.

nRF Cloud obtains public keys in one of the following ways:

  • Device key:

    • Upload the key manually with the RegisterPublicKeys endpoint.
    • nRF Cloud automatically extracts the device key from the device's non-JITP certificate during the provisioning process.
    • nRF Cloud automatically extracts the device key from the device's JITP certificate, if applicable and no other public key can be found to verify the signature.
  • Service key: nRF Cloud generates and stores the service key on demand through the Service Management interface. This requires a commercial plan. Contact Nordic Semiconductor Sales for more information.

JWT payloads

The payload for each JWT depends on the type of key used:

Signing (private) keyPayload
Device keyThe sub claim must contain the device ID. If your device is using its internal UUID as the device ID and modem_jwt_generate, omit the sub claim. Do not include the aud claim.
Service keyThe aud claim must contain your Team ID. The sub claim may contain a device ID if the request is servicing a single device.

Creating JWTs

The most secure way to use JWTs from devices is with the Modem JWT library or using the AT%JWT command directly. This requires modem firmware v1.3.x or later.

JWTs generated by the modem automatically contain the device UUID in the payload's iss claim. This is useful if your device uses its UUID as its device ID, in which case, you can omit the subject claim.

If your device uses a different value for the device ID, you must provide that value as the subject claim of the JWT. For example, if you want to use JWTs on Nordic Semiconductor products that have a device ID formatted as nrf-[IMEI], as is the case for the nRF9160 DK and Thingy:91, you must either provision a new certificate that uses the UUID (and re-provision the device on nRF Cloud), or pass the nrf-[IMEI] ID as the subject to the AT%JWT command.

Using JWTs in requests

Add the JWT to the Authorization header as a Bearer token. Here is a cURL example:

-H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkZXZpY2VJZGVudGlmaWVyIjoiZmIwOWNkZmItZTY4Yy00NGUzLWIwMTQtMmJlZDc4Yzk3OTQ5In0.RUAWePWjqRn4TK6EXsiKrsMM69FqDjg7dn52hrqG8CM"

REST client tools

You can call the REST API with a REST client tool such as Insomnia or Postman.

Use cURL or other utilities to call APIs from the command line.

If-match headers

API endpoints that change existing resources, such as UpdateDeviceName, allow you to include an optional If-Match header to avoid lost updates.

The value for this header is taken from the $meta.version property. The value is also available in the ETag for endpoints that return a single resource, for example, FetchDevice.

If the version you pass is not equal to the latest version of the resource, you get an HTTP 412 and PreconditionFailedError.

Additional resources

See the following guides for next steps: