System Overview

Everything you need to know about how Voodoo Robotics integrates with your warehouse management system.

What Voodoo Integrates With

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.

System Architecture

The Voodoo Robotics system consists of four layers: your application, the server, Turbos (signal routers), and Cloud Display Devices. Here's how they connect:

Your WMS/ERP sends API requests (REST or QueryString) to the Voodoo server.
Big Block Server (on-premise) or www.voodoodevices.com (cloud) processes commands, manages devices, and handles sequencing.
Turbos act as signal routers, bridging WiFi/Ethernet to the proprietary radio protocol used by devices. Plan roughly ~100 ft per Turbo (site dependent). Use more for redundancy and tougher RF environments.
Cloud Display Devices receive commands and display text, barcodes, QR codes, icons, and quantities. Workers press the button to acknowledge picks.

Integration Options

Voodoo Robotics supports two different APIs for interacting with Cloud Display Devices:

REST

REST API

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

GET

QueryString API

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

Use the REST API as your default integration path. If you need the fastest possible proof of concept or are working with a limited client, the QueryString API is a practical fallback. Both APIs use the same server and authentication, so you can mix and match.

Server Choices

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

What IT Needs to Provide

To deploy Voodoo Robotics in your facility, your IT team will need to provide:

✓
Network connectivity — WiFi or Ethernet drops for each Turbo. Turbos support DHCP and connect via standard WiFi or Ethernet.
✓
Power — AC power or Power over Ethernet (PoE) for each Turbo. Cloud Display Devices run on two AAA batteries (no wiring needed).
✓
Firewall rules (usually none needed) — Turbos act like any internal PC: they get an IP address via DHCP and make outbound HTTPS requests on port 443. This works on most networks without any configuration. For Big Block on-premise deployments, ensure Turbos can reach the server on your LAN.
✓
Server (Big Block only) — A Linux server to host the Big Block application.

Avoid Private-Only IPs for Big Block

Installing Big Block on a private IP address without a public-facing component means you cannot obtain an SSL certificate, forcing all traffic to use unencrypted HTTP. We strongly recommend using a public IP with HTTPS for production deployments.

Quick Example

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}
)

Quick Links

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

Next Steps

Getting Started

Step-by-step quickstart guide

Commands vs. Statics

Essential guide to API behavior and field classification

Authentication

Choose and configure your auth method

Server & Deployment

www.voodoodevices.com vs Big Block Server

REST API Overview

Full API endpoint reference