Skip to main content

Register Your Device

Overview​

This tutorial walks through the 2-Provisioning&Activation Postman collection. By the end, your WEDA Node device will be registered to WEDA Cloud and ready to report telemetry.

Prerequisites​

  • Completed Get Access Token — accessToken is set
  • Completed Manage Organizations — org_id is set
  • Your device's hwModel (e.g. MIC-710) and deviceId — available from the WEDA Node startup output

Variables You Set​

Unlike the earlier collections, deviceId is not auto-generated — you must set it yourself in the environment before registering.

VariableHow it's setUsed by
deviceIdSet manually — the device's MAC address (e.g. cc827f50f406), from WEDA Node startup outputNode Register, Collections 3 (Telemetry) and 5 (Tunnel)
hwModelSet manually — the hardware model string (e.g. MIC-710)Node Register
dataStreamIdCaptured automatically by the Data Stream List request in Collection 3 — nothing to set hereCollection 3 (Telemetry)

The Node Register request references hwModel and deviceId and auto-composes deviceName as {{hwModel}}-{{deviceId}}.

Registration Flow​

Run these three requests in order to register and activate your device:

  1. Node Register — creates the device record in WEDA Cloud
  2. Node Activation — retrieves the auth config needed to connect WEDA Node on the physical device
  3. Node List Under Org — verify the device status is Activated after WEDA Node connects

WEDA Token Refresh is a utility you can run at any point — use it to extend your accessToken without repeating the full SSO flow.

WEDA Token Refresh​

Refreshes your accessToken using the stored refreshToken, without repeating the full SSO login.

  • Script: accessToken and all token fields updated in the environment automatically
  • Result: 201 Created — accessToken is renewed
tip

The accessToken expires after 2 hours. Run WEDA Token Refresh whenever needed rather than re-running the entire 0-WiseSso collection.

Node Register​

Registers the device in WEDA Cloud under the current org_id. Set hwModel (e.g. MIC-710) and deviceId in your environment first — the request body references both and pre-fills deviceName as {{hwModel}}-{{deviceId}}. deviceName is optional; if omitted entirely, WEDA Core auto-generates the same {hwModel}-{deviceId} format server-side.

  • API: Register Device
  • Script: deviceId is not auto-generated — you must set it manually in the environment before sending
  • Result: 201 Created
note

deviceId is used by Collections 3 and 5. If you register multiple devices, update deviceId in the environment before switching collections.

Node Activation​

Retrieves the connection credentials that the WEDA Node agent needs to connect to WEDA Cloud.

  • API: Get Device Auth Info
  • Result: 200 OK — response contains the connection credentials; copy to your edge device to complete activation

Query & Management Operations​

These requests are independent — run them as needed, in any order.

Node List​

Lists all devices you have permission to view across your account.

  • API: List Devices
  • Result: 200 OK — a paginated list of devices

Node List Under Org​

Lists devices registered under the current org_id. Use this to verify a device's status after activation.

Node Deactivate​

Deactivates the device. The device stops reporting telemetry but its record remains in WEDA Cloud.

Node Remove​

Removes the device record from WEDA Cloud. Deactivate the device first.

note

In v1.1.1 this is a soft delete — the record stops appearing in queries but the underlying data is retained. Re-registering the same device in the same Org reconnects it to its existing DataStreams. See Device Management for the full deletion semantics.

Discovering What the Device Reports​

Once the device is Activated and syncing, each sensor it reports becomes a DataStream. Use the Data Stream List request in the Read Telemetry Data collection to see them — it also captures dataStreamId into your environment for the requests that follow.

note

See DataStreams for how a device's sensors become queryable DataStreams.

Last updated on Aug-2, 2026 | Version 1.1.1

On this page ...

Is this helpful?