GetWOListByUpdated
Lists the IDs of the work orders whose event or data field with a given code was saved in a period.
An integration calls it on a schedule to pick up what changed in TrakIT, for example every work
order whose gate-out event was recorded since the last call, then reads each one with
GetWO or reads just the values it needs with
GetSeqData.
How to sign in and read the response: Authentication, Responses.
GET /api/v1/GetWOListByUpdated?Code=GATEOUT&FromDate=2026-10-27&ToDate=2026-10-27T23:59:59&WFID=12Token: your-token| Parameter | Required | Meaning |
|---|---|---|
Code |
Yes | The code of an event or data field, for example GATEOUT. Capitals do not matter. Show Codes on a work order’s Events tab shows the codes. |
FromDate |
Yes | The start of the period, in UTC: a date, yyyy-MM-dd, or a date and time, yyyy-MM-ddTHH:mm:ss. |
ToDate |
Yes | The end of the period, in UTC, in the same form. At most 365 days after FromDate. |
WFID |
No | Only the work orders of this workflow: its ID, a whole number, as in the ID column of Workflow Definitions. The default, 0, is every workflow. |
JobType |
No | Only the work orders whose job has this job type, among others: the job type’s ID, a whole number. TrakIT Support can give you the IDs. The default, 0, is every job type. |
- Send
Code,FromDateandToDate. Without one of them the request does not reach the endpoint, and TrakIT answers with HTTP status 404 (see Errors). - Both ends are included. A date without a time means midnight at the start of that day, so
ToDate=2026-10-27leaves out what was saved later on 27 October. To include that whole day, send2026-10-27T23:59:59or2026-10-28. - Write a time with the
T, as above. TrakIT removes spaces from the dates, so2026-10-27 23:59:59is refused. See Dates and times.
What counts as a change
Section titled “What counts as a change”A work order is listed when the value of its event or data field with that code was last saved in
the period, its Updated time in GetWO. Only the last save
counts: a value saved in your period and again after it is listed only in the later period. Ask
for back-to-back periods, each starting where the last one ended, and every work order whose value
is saved is listed at least once.
Work orders of every status are listed, closed and cancelled ones included. A work order whose workflow has no event or data field with that code is never listed.
| Rule | Info when it fails |
|---|---|
The Token header holds a valid token. |
Token missing in header, Token invalid or expired, or another answer listed in Login token |
| The user is a system administrator with API access. | API User must be SysAdmin with API Access |
Code is not empty. |
Code is required |
FromDate is not empty. |
FromDate is required |
ToDate is not empty. |
ToDate is required |
FromDate is a date. |
FromDate is not valid |
ToDate is a date. |
ToDate is not valid |
ToDate is not before FromDate. |
ToDate must be later than FromDate |
| The dates are at most 365 days apart. | Days between FromDate and ToDate cannot exceed 365 |
Response
Section titled “Response”On success, RetInfo lists the work order IDs, in ascending order, each once, and RowsAffected is
how many there are.
{ "Code": 1, "Info": "", "RetInfo": [48211, 48212, 48305], "RowsAffected": 3, "Scalar": null, "Identity": 0}When no value with that code was saved in the period, the answer has Code 0 and Info
No data found.

