Get pauses

What it is: the dashboard’s «Reportes», tab «Pausas». A «pausa» is a stop one «operario» takes at their «puesto» with «Pausar» on the app, ended with «Reanudar», by an administrador from the board, or by the system (end of the «jornada», the «operario» leaving the «puesto», the feature going off). It is not a «descanso» (a «módulo»’s scheduled break) and not one of «Analítica»’s «pausas sin registro» (gaps inferred from the «marcas» log).

What it returns: rows, one per «pausa» that started in the range, newest first, at most 2000; summary, the figures over every «pausa» of the range, never only the rows sent; and truncated, true when the range holds more than rows carries (then narrow the range or filter). moduleId keeps the «pausas» of that «módulo»’s «puestos», operatorId the ones that «operario» started.

Durations are in minutes. durationMinutes is the whole «pausa» by the clock; minutes is what it took off the «puesto»’s «metas» (its part inside the «jornada» and outside «descansos»), the figure the other reports’ pausedMinutes add up. Both are null while the «pausa» is open. summary counts by the clock: its minutes, averageMinutes and longestMinutes are over durationMinutes.

Range: from and to are plant days, both included, at most 31 days apart counting both (RANGE_TOO_LARGE past it; note the cap is shorter than the efficiency charts’).

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. startMinute and endMinute are minutes of the plant day on that clock (0 is 00:00); startedAt and endedAt are the same moments as instants, ISO 8601 in UTC.

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 pauses («Pausas»), 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: "pauses". getPlan features lists what the organization’s plan has. On a plan that has it, a plant that never switched on «Habilitar pausas» answers 200 with no rows.

Heavy read: besides the credential’s ordinary budget it spends the heavy one, 20 requests per 60 seconds per credential and organization; past it the answer is 429 RATE_LIMITED with Retry-After.

Parámetros de ruta

Parámetros de consulta

Respuestas

curl -X GET "https://api.fluenta.io/v1/external/organizations/0/analytics/pauses?from=2026-10-01&to=2026-10-31" \  -H "Authorization: Bearer fluenta_live_XXXX"

{  "from": "string",  "to": "string",  "rows": [    {      "pauseId": "0cd3c330-3f92-4dc6-9dd9-8dc613a915e2",      "day": "string",      "moduleId": 0,      "moduleName": "string",      "operationId": 0,      "operationName": "string",      "operationPosition": 0,      "operatorId": 0,      "operatorName": "string",      "startedAt": "2019-08-24T14:15:22Z",      "endedAt": "2019-08-24T14:15:22Z",      "startMinute": 0,      "endMinute": 0,      "durationMinutes": 0,      "minutes": 0,      "endedBy": "operator",      "endedByName": "string"    }  ],  "summary": {    "count": 0,    "openCount": 0,    "minutes": 0,    "averageMinutes": 0,    "longestMinutes": 0,    "operators": 0  },  "truncated": true}