Retrieve a Production Log

Search Production Logs by machine, shift, SKU, date, quantity or review state. A POST because the filter body nests, but it only reads: the production_logs.read scope is sufficient. Send {} to get the first page with the defaults (page 1, limit 10). Filters are optional and combine with AND. Pages. Logs are ordered by start, then by id. The response gives totalCount and totalPages; request page 1, 2, … up to totalPages with the same filters and limit to read them all. A log written while you page can shift later pages by one. Dates. startDate filters on when a log starts and endDate on when it ends. after and before exclude the time itself, between includes both ends, and equal matches the exact time. Give times with a UTC offset. A shift's logs. To read back what a shift holds, for example after adding defects to it, filter by its id from GET /v1/shifts: `json {"shifts": {"include": [48213]}, "type": {"include": ["defects"]}, "limit": 100, "page": 1} ` A log is in a shift when it is on the shift's machine and lies within the shift. For only the defects, GET /v1/shifts/{shift_id}/defects returns the same logs in one unpaginated list.