Verify with Bruno

Use the Bruno collection to verify authentication, device listing, one real-time device-state query, and an optional control command. This is the recommended complete verification before writing integration code.

Before You Start

• Prepare clientId and clientSecret.
• Enable device:read.
• Enable device:control only if you will run the optional relay command.
• Confirm that the target device and relay are safe to control.

1. Install Bruno

Download the Bruno desktop app. For CI or headless environments, install the CLI:

npm install -g @usebruno/cli
bru --version

2. Open the Collection

git clone https://github.com/svnwi/wlte-openapi-sdk.git

Open this folder in Bruno:

examples/bruno/WLTE-OpenAPI/

3. Configure the Environment

Open environments/quickstart.bru and replace only:

clientId     ->  your_client_id
clientSecret ->  your_client_secret

Select the quickstart environment. Collection scripts populate accessToken, deviceId, and commandId; relayIndex defaults to 1.

4. Run Read-only Verification

Run these requests in order:

Order	Request	Purpose
1	00-auth / Auth	Obtain an access token
2	01-device-queries / 01-list-devices	Confirm accessible devices
3	01-device-queries / 02-get-device-real-time-status	Refresh and read one device state

The built-in assertions validate the HTTP status and response shape.

5. Optionally Verify Control

Device commands change real hardware. Continue only when the API Client has device:control and the operation is safe.

Order	Request	Purpose
4	02-relay-control / 01-turn-relay-on	Submit one relay command
5	03-command-result / 01-get-command-result	Read the command result

Skip this section for read-only integrations.

CLI Usage

cd examples/bruno/WLTE-OpenAPI
bru run --env quickstart

For a first integration, the desktop app is easier for inspecting environment variables, assertions, and response bodies.

Verification Result

After completing this page, you have verified:

• API Client authentication
• Device access and list responses
• Single-device real-time state
• Optional command submission and result lookup

Do not use repeated single-device requests to monitor an entire account. Use device lists for bulk views and WebSocket events for continuous changes.

Next Steps

• Integrate an SDK
• Review common failures
• Choose REST API or WebSocket