GetSeqData
Reads the events and data fields of a work order: for each one, its code, type, value and remarks, and who changed it last. These are the rows of the work order’s Events and Data tabs. Use it to check what is recorded before you save values. To find the work orders where a field changed, use GetWOListByUpdated; GetWO returns a whole work order, events and data included.
How to sign in and read the response: Authentication, Responses.
GET /api/v1/GetSeqData?WOID=48211&Code=GATEIN,CUSTREFToken: your-token| Parameter | Required | Meaning |
|---|---|---|
WOID |
Yes | The work order’s ID, a whole number. |
Code |
Yes, can be empty | The codes of the events and data fields to return, separated by commas and without spaces, for example GATEIN,CUSTREF. Codes are not case-sensitive. Leave it empty (Code=) to get all the work order’s events and data fields. |
Put both parameters in the query string, even when Code is empty. Without them, the request does
not reach the endpoint and TrakIT answers with HTTP 404.
To read several work orders, send one request for each.
| Rule | Info when it fails |
|---|---|
WOID has a value. |
WOID missing |
WOID is a whole number, not negative. |
All WOID must be integers |
| Each code has only letters, digits, underscores and hyphens. | One or more codes are invalid |
Without codes, WOID names one work order. |
If Code is not specifed, only one WOID can be specified |
| At most 1,000 codes are asked for. | Result cannot exceed 1000 items |
Response
Section titled “Response”On success, Code is 1, RetInfo is the list of events and data fields and RowsAffected is how
many there are. Identity and Scalar are not used. The events come first, then the data fields,
each in the workflow’s order.
Codes that the work order does not have are left out. If none of the codes is found, or the work
order does not exist, Code is 0 and Info is No data found.
{ "Code": 1, "Info": "", "RetInfo": [ { "WOID": 48211, "Code": "GATEIN", "Type": "Event", "FullName": "Gate In at Terminal", "Value": "2026-10-20 09:30", "ValueID": 0, "Remarks": "Gate 3", "UpdatedBy": "jsmith", "UpdatedOn": "2026-10-20T09:41:12.507" }, { "WOID": 48211, "Code": "CUSTREF", "Type": "Text", "FullName": "Customer Reference", "Value": "PO-77310", "ValueID": 0, "Remarks": null, "UpdatedBy": "jsmith", "UpdatedOn": "2026-10-18T14:02:55.18" } ], "RowsAffected": 2, "Scalar": null, "Identity": 0}| Field | Meaning |
|---|---|
WOID |
The work order’s ID. |
Code |
The event or data field’s code. |
Type |
Event for an event. For a data field, its data type: Text, Number, Currency, Date, Computed, Hyperlink, Google Place, Phone, Geo Data (a location) or Entity. |
FullName |
The name TrakIT shows: the master name followed by the specific info. |
Value |
The value, as text. Events and date fields are yyyy-MM-dd HH:mm in UTC, or NA or TBA. Amounts are formatted with two decimals, for example 1,250.00. Several list items are separated by line breaks. An empty string means no value. See Dates. |
ValueID |
Not used by this endpoint: always 0. |
Remarks |
The remarks, or null. |
UpdatedBy |
The User ID of the person who last changed it, or null if no one has. |
UpdatedOn |
When it was last changed, in UTC, or null. |

