Bioactive + IT in one platform
Readings from your terrarium become cloud data you can inspect in our dashboard and process in your own software.
FOR DEVELOPERS
WHY THIS EXISTS
Phasmida is built for people who want more than a closed gadget. Run your own hardware, send data to our cloud, observe everything in the dashboard, and keep API-level control for your own tooling.
Readings from your terrarium become cloud data you can inspect in our dashboard and process in your own software.
Build your own ESP32-based setup, request a key, and connect to Phasmida Cloud — no waiting for a closed ecosystem.
Each key identifies one physical device and uses MAC binding to reduce key sharing and cloning risks.
The API is in beta and evolving fast. Reliable auth core now, telemetry and claim flows next.
HOW IT WORKS
Request a key for your setup. Free tier is available in beta — register and we issue the key manually.
Store the key in your device firmware and send it as a Bearer token on every HTTP request.
On the first valid call the backend binds your reported MAC address to that key. Subsequent calls from a different MAC are rejected with 403.
Use the Smart Cloud dashboard for visibility and the API path for custom automations, tools, and workflows.
API KEY TYPES
One key, one active device. You request a key once, flash it into your firmware, and every request is authenticated with it as a Bearer token. Need to move the key to a different device? Unbind it from the Smart Cloud dashboard — the key becomes re-bindable on the next request.
For makers, tinkerers, and developers who build their own ESP32-based setup and want to connect it to Phasmida Cloud.
Every Phasmida-manufactured device ships with a pre-issued bundled key — flashed and ready on arrival.
BETA API TODAY
v1 backend is production-shaped but still beta: stable enough to build against, intentionally narrow in scope, and expanding in documented iterations.
| Code | Meaning |
|---|---|
200 | Key valid, MAC matches — request accepted |
401 | Missing or malformed Authorization header; key not found |
403 | Key revoked, or MAC mismatch (different device) |
Telemetry endpoint and claim flow are next iterations. Start with the identity layer now, then evolve with us.
Request (beta)
POST /health
Authorization: Bearer <api_key>
Content-Type: application/json
{
"macaddress": "AA:BB:CC:DD:EE:FF",
"firmware_version": "1.0.0",
"ssid": "terrarium-lab"
}First call — MAC binding
// mac_address is null → bound on first call // bound_at timestamp set // all future calls must match this MAC
Key exposed only once at issuance — store it immediately, it is not recoverable.
DEVICE LIFECYCLE
The MAC binding model ensures a single API key can only talk to one physical device at a time. If you replace a device or repurpose a key, you unbind via the Smart Cloud dashboard — no new key needed.
Automatic on the first request. The MAC address reported by your firmware is stored and locked to this key.
Available from the Smart Cloud dashboard. Clears the MAC binding — the next valid request will bind to the new device's MAC.
Permanent disable. Use if a key is compromised or the device is decommissioned. Revocation cannot be undone — issue a new key instead.
ROADMAP
The API grows in planned iterations. Build against v1 now — the auth model is stable and future endpoints follow the same key + MAC pattern.
Backend hosted in the EU. Your sensor data stays in Europe.
START BUILDING
Free beta key available now. If you are building a serious deployment, talk to us.