🇷🇺 RU🇬🇧 EN

REST API Documentation

Base URL: https://api.node07.xyz • Format: application/json; charset=utf-8 • POST limit: 8 КБ • Rate limit: 15 req/s

GET/api/ping

Check internet connectivity and node uptime. Minimal payload size allows parsing without large RAM buffers.

Request and response example
$ curl -s https://api.node07.xyz/api/ping
{"status":"ok","message":"pong","node":"node07","uptime_sec":3600,"requests":42191}
FieldTypeDescription
statusstringNode status (always "ok" during normal operation)
messagestringControl response "pong"
uptime_secintContinuous server uptime in seconds

  
GET/api/time

Fetch accurate time over HTTP/HTTPS to sync controller RTC clocks in networks where UDP port 123 (NTP) is blocked.

Request and response example
$ curl -s https://api.node07.xyz/api/time
{"unix":1794808000,"iso":"2026-11-16T05:46:40+00:00","utc":"2026-11-16 05:46:40"}
FieldTypeDescription
unixintSeconds since January 1, 1970 (UTC)
isostringDate and time in ISO-8601 format
utcstringHuman-readable time string in UTC timezone

  
GET/api/headers

Returns HTTP headers received by the server from the controller. Helps debug User-Agent, auth tokens, and proxies.

Request and response example
$ curl -s https://api.node07.xyz/api/headers
{"headers":{"host":"api.node07.xyz","user-agent":"ESP32HTTPClient"},"protocol":"HTTP/1.1"}
FieldTypeDescription
headersobjectDictionary of all incoming HTTP headers in lowercase
protocolstringClient HTTP protocol version

  
GET/api/uuid

Generate a random unique UUID v4 identifier. Useful for assigning unique device IDs on boards without hardware RNG.

Request and response example
$ curl -s https://api.node07.xyz
{"uuid":"550e8400-e29b-41d4-a716-446655440000"}
FieldTypeDescription
uuidstringRandom 128-bit identifier in UUID v4 format

  
POST/api/echo

Echo endpoint to verify JSON telemetry payloads from firmware. Accepts up to 8192 bytes and echoes it back with a timestamp.

Request and response example
$ curl -s -X POST https://api.node07.xyz/api/echo -H "Content-Type: application/json" -d '{"temp":23.5}'
{"received":{"temp":23.5},"timestamp":1794808000}
FieldTypeDescription
receivedanyParsed JSON object from request body (or raw)
timestampintUnix timestamp when the packet was received

  

HTTP Response Codes

CodeStatusReason
200OKRequest processed successfully
400Bad RequestInvalid header Content-Length
404Not FoundUnknown API route
413Payload Too LargePOST request body exceeds 8 KB limit
429Too Many RequestsRequest rate limit exceeded (15 req/s)

Negative Response Examples

For application-level errors, the API returns a JSON object with the error. When web server rate limiting (429) is triggered, a standard Nginx response is returned.

404 Not Found — request to a non-existent path
{"error": "not found"}
413 Payload Too Large — POST body exceeds 8192 bytes
{"error": "payload too large"}
400 Bad Request — malformed Content-Length header
{"error": "bad length"}
429 Too Many Requests — rate limit of 15 req/s exceeded (Nginx response)
<html><head><title>429 Too Many Requests</title></head>...