The Voodoo Three Layer Architecture
Watch Voodoo Robotics' four-video overview of the system architecture.
Open playlist on YouTubeEverything you need to know about how Voodoo Robotics integrates with your warehouse management system.
Voodoo Robotics Cloud Display Devices work with any warehouse management system (WMS), enterprise resource planning system (ERP), or custom application that can make HTTP requests. Integration is straightforward — your system sends commands via a simple API, and the devices light up, flash, display text, barcodes, QR codes, arrows, and quantities to guide workers on the warehouse floor.
Common integration partners include SAP, Oracle WMS, Manhattan Associates, Blue Yonder, Infor, Fishbowl, and dozens of custom-built systems. If your platform can issue an HTTP GET or POST request, it can drive Voodoo devices.
Before building a connector, review the existing integration examples. Voodoo publishes reusable code for several common WMS, ERP, accounting, and shipping platforms.
The Voodoo Robotics system consists of four layers: your application, the server, Turbos (signal routers), and Cloud Display Devices. Here's how they connect:
This four-video playlist gives you a guided tour of the Voodoo system architecture. You can play the entire series here or open the playlist on YouTube. The series calls the Device, Turbo, and server the three Voodoo layers; the diagram above also includes your application as the fourth integration layer.
Watch Voodoo Robotics' four-video overview of the system architecture.
Open playlist on YouTubeVoodoo Robotics supports two different APIs for interacting with Cloud Display Devices:
Full-featured JSON-based REST interface. Supports device management, bulk updates, locations, orders, sequences, and closed-loop acknowledgements. This is the recommended approach for production.
Best for: Production deployments, advanced features
The simplest possible integration. Construct a URL with query parameters and issue a GET request. Great for initial evaluation, simple one-device commands, and systems with limited HTTP capabilities.
Best for: Quick prototyping, simple integrations
Recommended Path
Voodoo Robotics provides two server deployment options:
| Feature | www.voodoodevices.com | Big Block Server |
|---|---|---|
| Hosting | AWS (managed by Voodoo) | On-premise or your cloud |
| Device Limit | Up to 50 devices | Unlimited |
| Internet Required | Yes | No (runs on LAN) |
| Sequencer | Limited | Full |
| Latency | ~1.3 seconds | ~0.9 seconds |
| Best For | Starter kits, evaluation | Production, >50 devices |
To deploy Voodoo Robotics in your facility, your IT team will need to provide:
Avoid Private-Only IPs for Big Block
In just five lines of Python, you can send a command to a Cloud Display Device:
import requests, json
session = requests.Session()
url = "https://www.voodoodevices.com/api/"
# Login
x = session.post(url + "user/login/",
json={'username': 'yourusername', 'password': 'yourpassword'})
z = json.loads(x.text)
# Send a command to a device
session.post(
url + "device/E8D008:619874/",
headers={'referer': url, 'x-csrf-token': z['token']},
json={'command': 'flash', 'line1': 'Hello', 'line2': 'World', 'seconds': 60}
)# Using API-KEY authentication
curl -X POST "https://www.voodoodevices.com/api/device/E8D008:619874/" \
-H "API-KEY: your-api-key" \
-H "Content-Type: application/json" \
-d '{"command": "flash", "line1": "Hello", "line2": "World", "seconds": 60}'Getting Started
Quickstart checklist and first test
Authentication
API-KEY, Session, OAuth2 methods
REST API Reference
Endpoints, examples, and responses
Starter Kit
What's in the box and how to evaluate
Devices & Networking
Turbos, placement, and connectivity
Best Practices
Display conventions and deployment tips