Structured Content, Delivered to Anything That Can Ask for It
Zunoy's content API returns plain structured JSON over HTTP, consumable by any client that can make a request — a website, a dashboard, or a connected device.
Standard REST API over HTTP
One content model, every surface
Draft and publish states built in
WHAT THIS ACTUALLY MEANS
One Content Model, Read by Whatever Needs It
A content type you define once — a device manual, a firmware release note, a support article, a remote configuration value — is available as structured JSON to any client that can issue an HTTP request, without a device-specific integration to build.
Nothing Proprietary
Structured JSON over standard HTTP
No Duplication
One content model instead of duplicating copy across surfaces
Draft, Then Publish
Draft and publish states keep unfinished changes off production reads
Common Questions
Does Zunoy have IoT-specific protocol support?
No. Zunoy does not support device protocols like MQTT or CoAP, and there is no device-side SDK. It offers a standard REST content API over HTTP, which any client capable of making an HTTP request can consume.
Can a device read content directly from Zunoy?
If the device or its companion software can make an HTTP request and parse JSON, yes. Beyond that, there is no device-specific delivery mechanism.
What kind of content actually fits this use case?
Content that supports a connected device rather than runs on it — companion app copy, setup instructions, firmware release notes, and support articles — kept in one structured model instead of duplicated across surfaces.
One Content Model for Every Surface Around Your Product
Website, app, dashboard, or device — the same structured content, read the same way.