Developers · Open platform

Build on the platform, not around it.

HERO is one client of the API — not the only one. Read fleet state and history, subscribe to events, and push software to machines over the air, through a documented REST API authenticated per tenant. If your team can call HTTP, it can build on DMS.

Request API access See the platform
REST + JSON Webhooks Per-tenant auth

Integration philosophy

Open at both ends

The platform is not a black box with a login. The same data your operators see in HERO is available over an API, and the same OTA pipeline that ships our software can carry yours. We design for integration, not lock-in.

  • One source of truth

    Devices, transactions and telemetry live in QuadC; the API reads and writes the same records HERO does — no export lag, no second copy.

  • Authenticated per tenant

    Every call is scoped to your fleet with a tenant key. You see your machines and no one else's.

  • Honest, versioned surface

    A stable REST contract we document and version — not a private endpoint that changes under you.

REST API

The surface, described honestly

An overview of what the API exposes today. Full reference, request and response schemas and a sandbox key come with access — ask and we'll set you up.

BASE https://api.dms-tech.com/v1
  • GET /devices List machines in your fleet with status, model and last-seen.
  • GET /devices/{id} One machine: configuration, health and current online state.
  • GET /transactions Sales and payment records, filterable by machine, method and date.
  • GET /telemetry Typed telemetry events — stock, temperature, faults, uptime — per machine.
  • POST /devices/{id}/commands Send a machine a command: enable, disable, reconfigure, price.
  • POST /webhooks Register an endpoint to receive events as they happen.

Responses are JSON; pagination and filtering are query parameters; errors carry a machine-readable code and a human message.

Webhooks

Get the event, don't poll for it

Subscribe once and the platform pushes events to your endpoint as they occur — so your systems react to a sale or a fault in seconds, without hammering the API.

transaction.completed A payment cleared on a machine — amount, method, machine and time.
machine.fault A machine raised a fault — code, machine and severity — the moment it trips.
stock.low A slot crossed its low-stock threshold and needs a refill.
machine.offline A machine dropped off the network, or came back online.

OTA pipeline

Ship software to the field from an API call

The over-the-air pipeline that distributes Hero Nexus builds is scriptable. Roll a build to a group, watch it, widen it, and roll back — from HERO or from your own tooling through the API.

  • Target by group

    Release to one machine, a site, a region or the whole fleet — you choose the cohort.

  • Staged and observable

    Watch adoption and health as a build rolls out; the pipeline reports progress per machine.

  • Reversible

    If a build misbehaves, roll the cohort back to the previous version without a site visit.

Integration paths

Two ways in

Whether you build machines or connect them, there is a defined path. Tell us which one you are and we'll point you at the right surface.

OEMs & machine builders Ship machines that are connected out of the box. Hero Nexus runs on the terminal you choose; we map your machine's control interface once.
  1. Pick a supported terminal
  2. Map the machine over MDB / Executive / Modbus
  3. Ship it cloud-connected
System integrators Fold fleet data into the systems an operator already runs — ERP, accounting, BI — using the REST API and webhooks.
  1. Get a tenant sandbox key
  2. Pull devices, transactions, telemetry
  3. Subscribe to webhooks for live events

Get a sandbox key

Tell us what you're building and who you are — an OEM, an integrator, an operator with a dev team. We'll send API docs and set up a sandbox tenant.

Request API access Explore QuadC