SaveSeqDataAsync

Takes the same items as SaveSeqData, but answers at once and saves them in the background. When all the items have been processed, TrakIT posts the results to a URL you give, if you give one.

How to sign in and read the response: Authentication, Responses.

Which one to use

	SaveSeqData	SaveSeqDataAsync
TrakIT answers	When every item has been processed.	At once, before any item is checked.
Results of the items	In the response.	Posted to your CallBack URL, or not at all.
Use it for	Small batches, and when you act on each item’s result.	Large batches that could exceed your timeout, and updates you do not need to follow up.

Both take at most 999 items per request, and check and save each item the same way.

Request

POST /api/v1/SaveSeqDataAsync?CallBack=https%3A%2F%2Fintegration.example.com%2Ftrakit%2Fresults%3Fbatch%3D20261020-01
Token: your-token
Content-Type: application/json

[
  { "WOID": 48211, "Code": "GATEIN", "Value": "2026-10-20T09:30:00", "Remarks": "Gate 3" },
  { "WOID": 48212, "Code": "GATEIN", "Value": "2026-10-20T09:42:00", "Remarks": "Gate 1" }
]

Parameter	Required	Meaning
CallBack	Yes, can be empty	The URL TrakIT posts the results to, URL-encoded. It must start with https://. Leave it empty (CallBack=) if you do not want the results: the items are saved all the same.

Put CallBack in the query string even when it is empty. Without it, the request does not reach the endpoint and TrakIT answers with HTTP 404. A value that does not start with https:// is accepted, but TrakIT then sends no results.

The body is the same JSON array of items as for SaveSeqData: see its fields and values.

Rules

Before it answers, TrakIT checks only the request as a whole:

Rule	Info when it fails
The body is a JSON array of items.	No data supplied or json is malformed
It has at most 999 items.	Count of data supplied must be less than 1000

Each item is then checked and saved in the background, as described in SaveSeqData’s rules. Their results are in the callback.

Response

The response only says that TrakIT has taken the items. Code is 1, and Info gives the number of items and the callback URL. RetInfo is null, and RowsAffected, Identity and Scalar are not used. A Code of 1 does not mean that the items were saved.

{
  "Code": 1,
  "Info": "Processing 2 items. Will callback https://integration.example.com/trakit/results?batch=20261020-01",
  "RetInfo": null,
  "RowsAffected": 0,
  "Scalar": null,
  "Identity": 0
}

Callback

When all the items have been processed, TrakIT sends one POST request to the CallBack URL. Its body is a JSON object, the same as the response of SaveSeqData: Code is 1 if at least one item was saved, RowsAffected is the number saved, and RetInfo has one result for each item, in the order sent.

{
  "Code": 1,
  "Info": null,
  "RetInfo": [
    { "WOID": 48211, "Code": "GATEIN", "Result": 1, "Info": "Success" },
    { "WOID": 48212, "Code": "GATEIN", "Result": 0, "Info": "Out of sequence" }
  ],
  "RowsAffected": 1,
  "Scalar": null,
  "Identity": 0
}

• The request has no Content-Type header: read its body as JSON whatever the header says.
• It carries no token or signature. Use a URL that is hard to guess, and treat the body as a notice: check the values with GetSeqData if you need to be sure.
• The body does not name the request it answers. To match it, put your own batch reference in the callback URL, as in the example above, or match the results by WOID and Code.
• TrakIT sends it once. It does not retry if your server cannot be reached or answers with an error, and it does not read your answer.

If no callback comes, check the values with GetSeqData before you send the items again. Items that are already saved come back Unchanged, so sending a batch again is safe.

Notes

• A save has the same effects as with SaveSeqData: computed fields, the work order’s status, the actions and the audit log. See SaveSeqData’s notes.
• Each request is processed on its own, in the background, so two requests can be processed at the same time. If the order of the changes matters, for example on the same work orders, wait for the first callback before you send the next batch.