IP Devices

OnboardDevice

Onboard and associate a single device with your nRF Cloud account.

Uploading a device certificate allows the device to use nRF Cloud services using any supported connectivity protocol, such as MQTT, and CoAP. This endpoint involves your own CA certificate and requires you to upload device certificates that you have already obtained, whether via a CSR produced by the AT%KEYGEN command (modem firmware v1.3+), or offline via your own script. We impose no rules on your CA certificate, and a self-signed certificate may be used. For more information see Onboarding in the nRF Cloud documentation.

Whether using our APIs via REST or MQTT you will need to flash to your device:

  1. <a href="https://www.amazontrust.com/repository/AmazonRootCA1.pem" target="_blank">The Amazon Root CA1 PEM file</a>, which enables the device to authenticate the AWS IoT server.
  2. The private key associated with the device certificate.

Additionally, if the device will be using MQTT, you will also need to flash the device certificate. For signing JWTs you will use the private key associated with the certificate. (During the device onboarding process we extract the corresponding public key from your uploaded certificate and use this for JWT signature verification.)

For bulk onboarding of devices, please use the OnboardDevices endpoint.

post/devices/{deviceId}

Path parameters

deviceIdstring required

This is the canonical device id used in the device certificate, and as the MQTT client id.

Example:nrf-1234567890123456789000

Request body

certificatestring required

X509 Certificate in PEM format.

subTypestring

A custom string value to specify the type of thing (device) being provisioned on nRF Cloud.

tagsDeviceTag[]
supportedFirmwareTypesFirmwareTypes[]

Firmware types supported by the device for FOTA.

Changes

No recorded changes to this endpoint across all 1 revision of this API.