Skip to main content

Changelog

Everything that changed in v1, newest first.

What counts as a breaking change​

Only breaking changes force a new version. This is the line:

ChangeBreaking?
New field in a responseNo — ignore what you do not use
New optional field accepted in a requestNo
New endpointNo
A field disappears or changes typeYes
A field changes meaningYes, and the worst kind — nothing errors
A route is renamedYes

A breaking change becomes v2, and v1 stays up. You should never have to migrate at the same moment your server is upgraded.


2026-11-09 — the ERP phases​

Additive. A file that does not send the new column sees no change.

  • An optional column, Phases: the phase codes of your ERP (CODE[*count][@mark], separated by commas), translated into services by the plant's phase mapping, instead of the ready-made list in Services. Both in the same row are rejected. In .xlsx it is found by its header (only the name Phases), like Weight. The rule is in file format.
  • The separators * and @ are provisional, to be confirmed against your ERP's codes.
  • A code the plant has not registered rejects the row, with the codes in the reason; send the row again once the plant registers it.

2026-11-09 — the edging allowance, and the header ignores letter case​

Additive. A file that does not send the new columns sees no change in what it sends; the piece uses the allowance of its glass type.

  • Two optional columns: EdgingAllowance (the same value on the four sides) and EdgingAllowanceSides (one per side, top-right-bottom-left, separated by hyphens). In .xlsx they are found by their header, like Weight. The rule is in file format.
  • The CSV header is matched ignoring letter case and the spaces around a name. A column that used to be ignored because of its letter case is now read.

2026-11-05 — a time zone in DueDate is refused​

Breaking for a file that sends a time zone, without a v2, by decision of the plant owner. A file that sends the plant's local time, which is what the samples and the Mover.Glass Connector do, sees no change.

You send in DueDateBeforeNow
Z or an offset: 2026-11-10T08:00:00Z, 2026-11-10T08:00:00+02:00CREATED, converted to the server's clock and stored as the plant's timeREJECTED, with the reason quoting the text
A time zone written by name: … GMT, … UTC, … CET, …+01:00[Europe/Rome]CREATED with the default date, silentlyREJECTED, like the Z
Text that cannot be read: 20261110, 2026-02-30, 08:00CREATED with the default date, silentlyCREATED with the default date and a warning on the item, quoting the text

The warning is a new field on the item, which you may ignore. Send YYYY-MM-DD or YYYY-MM-DDTHH:MM[:SS], in plant time. The rule is in file format.

2026-10-20 — the stage situation follows the plant's rule​

Breaking, without a v2, by decision of the plant owner. Three situations change meaning, one is new and scheduledFor moves by 3 hours. The old values were wrong (see below), and a v2 would have kept the wrong ones alive. Nothing in the HTTP response warns you: read this before the deployment.

WhatBeforeNow
LATEthe planned start had passedthe scheduled stage will finish after the date it must be ready by (or now is already past it); the stage with no schedule, once the piece's deadline has passed. A split lot is LATE if any part that has not started is late, even with another part in the machine, already passed or at the supplier
UNSCHEDULEDdid not exist: these stages came as WAITINGnew: not started, not scheduled yet, with the piece's deadline still ahead
WAITINGeverything not started and not lateonly a scheduled stage that is on time
scheduledFora local plant time sent with a Z: an instant 3 hours earlier than the real onethe real instant, in UTC

The 3 hours. The plant's local time used to be compared with UTC: LATE came out 3 hours early, and scheduledFor showed an instant 3 hours before the real one. If you added 3 hours to scheduledFor to compensate, stop on the day of the deployment.

If you generated an enum from the old list of situations, add UNSCHEDULED, or treat unknown situations as informative. The full rule is in production status.

2026-09-18 — routes and fields in English​

Breaking, and done without a v2. Until that day the only consumer of this API was our own Connector, in the same repository, so the rename cost nobody anything. Once you have written code against it, a change like this becomes a v2 — the only exceptions since then are the stage situation and the time zone in DueDate (the entries above), by decision of the plant owner.

WasIs now
/api/v1/integracao/conexao/api/v1/integration/connection
/api/v1/integracao/pecas/arquivo/api/v1/integration/pieces/import
/api/v1/integracao/situacao/api/v1/integration/production-status
multipart field arquivofile
codigoBarra, desfecho, motivobarcode, outcome, reason
CRIADA, IGNORADA, RECUSADACREATED, IGNORED, REJECTED
AGUARDANDO, ATRASADA, CONCLUIDAWAITING, LATE, DONE

POST /api/v1/integracao/pecas was removed. The single-piece endpoint had no consumer. If you need to push pieces one at a time rather than in a file, ask — it comes back as a documented endpoint rather than an accident.

The CSV column names are English too, and the Portuguese ones still work.

WasIs now
CodigoBarraBarcode
DescricaoDescription
Largura · AlturaWidth · Height
EspessuraThickness
ServicosAplicaveisServices
TipologiaGlassType
NomeClienteCustomerName
DataFinalizacaoDueDate
QtdeQuantity
InativaCancelled
PedidoCliente · PedidoInternoCustomerOrder · InternalOrder
UrgenteUrgent
ObservacaoNotes
RotaRoute
PrioridadePadraoPriority
RecortesCutouts
PecaPaiIdParentBarcode
Rc2Shape
SVGDrawing
ImagemPedidoOrderImage

Nothing breaks. Every name on the left is still accepted, so a file you already generate keeps working — the two sets can even share a header. Use the English ones for anything new: those are what this documentation will keep describing.

The .xlsx layout is read by position, so nothing changed there at all.

2026-09-18​

Numbers with a comma are read correctly. A measurement written 6,5 was being read as 65, because the comma was treated as a thousands separator. Thickness, width, height and quantity are affected, in all three file formats.

Unreadable numbers now refuse the piece with a reason, instead of becoming 0 in a measurement or 1 in a quantity. See how numbers are read.

If your system sends 1.234 meaning one thousand two hundred and thirty-four, that value is now refused as ambiguous — send 1234.

Fractional thickness works in spreadsheets. Excel files read thickness as a whole number, so 6.5 mm glass could not be imported at all, not even written with a dot.

2026-09-17​

Cancelled pieces are refused instead of created active. Inativa=True was read from the file and then dropped: the piece was created active, got a production route and entered the cutting plan, while the response said CREATED.

It now returns REJECTED and stores nothing — not the piece, not the glass type or customer it would have created. See cancelled pieces.

The deadline your system sends is preserved. A piece created through the single-piece endpoint had its dataFinalizacao overwritten with the moment of the request. An order due at the end of the year was born overdue on the same day.

Both service separators are accepted. The single-piece endpoint required a semicolon while the refusal message itself showed commas. Both now work.

2026-09-16​

The integration surface was published, with the guarantees described here: one API key per installation, three outcomes per piece, and per-piece transactions on file import.

Before this, a resend returned success silently, with no way to tell "created" from "already existed".