Get module day history

What it is: the hour-by-hour table of «Reportes por módulo» for one «módulo» (a production line) on one plant day, the numbers the dashboard shows there. hours holds one entry per clock hour that had a «marca» or a «pausa», in order; each totals the hour (units, goal, efficiency, billedAmount, secondsPerUnit, pausedMinutes, pauses) and lists, in rows, one row per «puesto» and «referencia» worked in it. An hour with «pausas» and no «marca» has no rows.

How it is computed: a row’s goal is that «puesto»’s «meta» for the hour as it stood then (already shortened for «descansos», «pausas» and the edges of the «jornada»); the hour’s goal is the sum of its «puestos»’ and its efficiency is its units × 100 ÷ that goal.

efficiency is «Eficiencia»: units made × 100 ÷ the «meta» of the same span, a percentage with 2 decimals (100 = exactly the goal, it can pass 100; never a 0–1 ratio), null where the goal is 0. Every «puesto» counts towards it, a «puesto de salida» or not.

Money is «Facturación»: the units of the «puestos de salida» × the price per unit each was billed at, in the plant’s currency (currency, ISO 4217: EUR for a plant in España, COP for every other), in whole currency units with up to 2 decimals, never cents. Whether a money figure reads null or 0 where nothing was priced is stated on each field. A row’s billedAmount is null on a «puesto» that is not «de salida»; the hour’s is the sum over the ones that are.

Days and hours are the plant’s own: a plant day is a calendar day YYYY-MM-DD in the organization’s timezone (getOrganization timezone), never UTC, and an hour is the clock hour 0–23 that starts at it in that zone. The day is the path’s day, required.

Naming: each row’s operationId is its «puesto» (a numbered station of a «módulo»). A «puesto» is an operation in ids, filters and codes and a station in paths: the same number is the id listStations returns and the stationId of the station routes.

Plan: needs the plan feature moduleReports («Reportes por módulo»), the one its dashboard screen is gated by. Pro, a trial of Pro and an «exenta» organization answer it; a Light organization, of either plan version, does not: 403 PLAN_LIMIT with feature: "moduleReports". getPlan features lists what the organization’s plan has.

See also: getHoursBoard for the same «módulo» and day as its «Tablero de producción» (typed counts, running totals), getModuleEfficiency for this «módulo» over a range, getStationDayReport for one of its «puestos».

Parámetros de ruta

Respuestas

curl -X GET "https://api.fluenta.io/v1/external/organizations/0/modules/0/days/2026-11-10/history" \  -H "Authorization: Bearer fluenta_live_XXXX"

{  "day": "string",  "module": {    "id": 0,    "name": "string"  },  "currency": "string",  "hours": [    {      "hour": 0,      "units": 0,      "goal": 0,      "efficiency": 0,      "billedAmount": 0,      "secondsPerUnit": 0,      "pausedMinutes": 0,      "pauses": 0,      "rows": [        {          "operationId": 0,          "operationName": "string",          "operatorId": 0,          "referenceId": 0,          "referenceName": "string",          "units": 0,          "goal": 0,          "efficiency": 0,          "isBilling": true,          "billedAmount": 0        }      ]    }  ]}