Build on SPIDEX.
Open where it matters, integrated where it creates value. Standard protocols at the boundaries, documented interfaces, and no expectation that the platform owns your architecture.
What you can build against.
REST API
Registry, telemetry, commands, configuration and audit over HTTP, authenticated per tenant.
MQTT
Device and application messaging over a standard broker interface with TLS.
Webhooks
Platform events pushed to your services as they happen.
C3F modules
Add device-side capability without forking the framework or the product.
Device integration
Bring a third-party or custom device onto the platform through the adapter model.
Export and retention
Configurable retention with export paths, so the data stays yours.
# List devices with a pending firmware update
curl -s https://api.spidex.tech/v1/devices \
-H "Authorization: Bearer $SPIDEX_TOKEN" \
-G -d "state=update_ready" -d "site=plant-2"
{
"count": 286,
"devices": [
{
"id": "SPX-GW-004183",
"model": "SPIGWAY EnI",
"firmware": { "current": "4.1.7", "staged": "4.2.1" },
"site": "plant-2",
"state": "update_ready",
"last_seen": "2026-03-14T09:41:22Z"
}
]
}Illustrative shape — see the API reference for the current contract
Reference material.
The developer portal, API reference and repositories are published as they become available. Links appear here once they are live rather than in advance.
API reference
Coming soonDevice integration guide
Coming soonC3F module guide
Coming soonRepositories
Coming soonWorking on an integration now? Ask for current documentation directly and we will send what exists today.
Integrating SPIDEX into something you already run?
Tell us what is on the other side of the integration and we will point you at the right interface — or tell you if it does not exist yet.