Skip to content

REQUEST / RESPONSE

Test HTTP device telemetry with visible request payloads.

Send a known request to your device’s ingest endpoint, inspect the received frame and compare the gateway response with what your firmware expects.

Start HTTP testing →Read the setup guide

SingleIoT product guide · Updated October 14, 2026

UNDERSTAND THE EXCHANGE

What can you test with HTTP?

HTTP testing helps you isolate problems in device telemetry uploads: the wrong endpoint, a rejected token, an unexpected body or a reply your firmware cannot parse. SingleIoT’s device ingest gateway captures the request payload and useful request metadata, so you can inspect the exchange rather than relying only on the device’s error message.

01

Request configuration

Check the ingest hostname, port, path and authentication method shown in your device workspace.

02

Received payload

Inspect JSON, text or binary bytes and compare the received request body with your source payload.

03

Gateway response

Validate custom acknowledgement behavior and inspect command replies during integration testing.

SET UP YOUR FIRST TEST

How to test a HTTP device in SingleIoT

  1. 1

    Create an HTTP device

    Choose HTTP and review the assigned connection details. Confirm whether the endpoint expects HTTP or HTTPS.

  2. 2

    Prepare a small test request

    Use POST /v1/ingest with a known body. For token authentication, include Authorization: Bearer followed by the device token.

  3. 3

    Send and inspect the frame

    Open the device’s live console and send the request. Check the received bytes, method, path and other captured metadata.

  4. 4

    Verify the response path

    Compare the response with the device’s expected status and body. When testing commands, use the supported command polling and reply paths shown in your workspace.

HTTP connection example

Start with a known message, then compare it with the captured frame.

HTTP · illustrative setup
curl --request POST "$DEVICE_INGEST_URL/v1/ingest" \
  --header "Authorization: Bearer $DEVICE_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{ "temperature": 26.5, "battery": 98 }'

Set DEVICE_INGEST_URL to the device gateway URL shown in your workspace, including its scheme and assigned port. Set DEVICE_TOKEN to your device token. The dashboard’s /api/ routes are separate from device ingest.

Common HTTP testing problems

Change one setting at a time and use captured traffic to verify the result.

Request is rejected

Check the token, device status and enabled protocol. Ensure the Authorization header reaches the assigned device gateway.

Payload never appears

Verify POST /v1/ingest, the correct gateway port and the selected device. A successful request to the website is not an ingest test.

HTTPS handshake fails

Confirm the certificate authority and server hostname expected by the endpoint. Use the configured trust material rather than disabling certificate validation.

Body is too large

Check your plan’s frame-size limit and reduce the payload for the first test. The gateway also applies a hard request-body limit.

HTTP testing questions

Can I send JSON and binary telemetry?

The ingest gateway accepts a request body as frame data. Set an appropriate Content-Type and inspect the captured payload using the views available in your workspace.

How are HTTP device commands delivered?

The gateway supports GET /v1/commands for the next queued command and POST /v1/ingest/reply for a device reply. Use the same assigned endpoint and supported device authentication.

See what your HTTP device actually sends.

Create a device workspace and inspect your first frame.

Create your workspace →