Skip to main content

Integrating with Mover.Glass

Mover.Glass is the MES that runs the glass shop floor: it takes the pieces your system ordered, schedules them, tracks them through every machine, and tells you where each one is.

This documentation covers one surface: /api/v1/integration/. Three endpoints, an API key, and a file format.

What you do, and what we do​

Integration fails most often because nobody wrote down who owns what. So here it is.

ResponsibilityWhoseWhat it means
The business keyYoursThe barcode identifies the piece. You choose it, you own it, and it is what you use to ask about the piece later
Not duplicatingOursSend the same barcode twice and the second one is ignored, not duplicated
RetryingYoursIf the network drops, send it again. That is safe by design
Knowing what happenedOursEvery piece you send comes back with an outcome, and every refusal comes back with a reason
Correcting dataYoursWe refuse bad data and say why. We never guess a plausible value

That last row is the one worth reading twice. If a measurement cannot be read with certainty, the piece is refused with a reason — it does not become zero, and it does not become "close enough". A refused piece is a message you can act on; a silently corrected one is glass cut to the wrong size.

What is not part of this contract​

Everything outside /api/v1/integration/.

Mover.Glass has many other endpoints. They serve our own web and mobile apps, they change without notice, and they are not documented here. If something you need is not on this surface, ask us to put it here rather than calling an internal route — an internal route working today is a coincidence, not a promise.

A note on names​

Routes, JSON fields and enum values are in English — and only here. Everything inside Mover.Glass is written in Portuguese, because the people reading that code every day are Brazilian, and the vocabulary of a Brazilian glass shop is more precise than its translation.

The translation happens at this boundary and nowhere else. That is deliberate: one place to change, one place to get wrong.

The names are stable. If they ever change, that is a v2 — the v1 keeps working, because you should never have to migrate at the same time as a server upgrade.

Where to start​

  1. Authentication — get a key and confirm it works
  2. Sending pieces — one piece, or a whole order file
  3. File format — the columns, and how numbers are read
  4. Production status — read back where every piece is