Why HTTP simulation matters
Modern IoT, building automation, and industrial systems expose REST endpoints for data access, configuration, and webhooks. Testing HTTP integrations against real backend services is slow, brittle, and often blocked by infrastructure dependencies. Teams need deterministic, controllable HTTP endpoints to validate client logic, webhook handling, and API contracts before connecting to production services.
SPX solves this by exposing HTTP REST endpoints backed by twin attributes. Teams can simulate weather feeds, air quality stations, vision systems, and custom REST APIs with full control over responses, payloads, and timing.
REST backends are slow, rate-limited, or unavailable for testing
API responses and webhook payloads need validation
HTTP exchanges are hard to debug against external services
Expose deterministic HTTP endpoints from twin attributes
What SPX simulates
SPX includes an HTTP endpoint adapter (http_endpoint) that exposes deterministic REST endpoints backed by attributes. Endpoints are served by FastAPI/uvicorn inside SPX Server and support GET, POST, PUT, and DELETE methods with JSON payloads.
GET, POST, PUT, and DELETE with JSON payloads
Weather feeds, air quality, and telemetry APIs
Change response data and latency at runtime
Reproducible error and edge-case scenarios
Core capabilities
HTTP simulation in SPX is built for API integration testing, webhook validation, and service-mock workflows.
Map HTTP routes to twin attributes
Steer response data and timing
Run HTTP mock tests in Docker and CI
Inspect HTTP requests and responses in real time
Example models
SPX ships with HTTP endpoint models for weather feeds, air quality stations, and vision systems.
Weather Forecast Feed (HTTP)
Air Quality Station (HTTP)
Smart Building Pack
Developer path
HTTP simulation connects directly to the model catalog, industry packs, and developer workflows.