GetEntitiesUpdated
Lists the entities that were created or changed in a period, with
their ID, code and name. An integration that keeps its own copy of your customers, suppliers and
other parties calls it on a schedule, then reads each entity listed with
GetEntity.
How to sign in and read the response: Authentication, Responses.
GET /api/v1/GetEntitiesUpdated?FromDate=2026-10-01&ToDate=2026-10-31T23:59:59Token: your-token| Parameter | Required | Meaning |
|---|---|---|
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. |
- Send both parameters. 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-31leaves out the changes made later on 31 October. To include that whole day, send2026-10-31T23:59:59or2026-11-01. - Write a time with the
T, as above. TrakIT removes spaces from the dates, so2026-10-31 23:59:59is refused. See Dates and times.
What counts as a change
Section titled “What counts as a change”An entity is listed when it was created, or when its details were last saved, in the period: with Edit Entity on the entity page or by an import. Disabling an entity is such a change.
These do not count: approving the entity, and changes to its entity data fields, documents, contacts, other types or company settings.
Only the last change counts: an entity changed 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 entity whose details change is listed at least once.
| 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 |
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 entities, in order of ID, and RowsAffected is how many there are.
The list has the entities of every type and every company, disabled ones included.
{ "Code": 1, "Info": "", "RetInfo": [ { "EntID": 48211, "EntCode": "EXSHIP", "EntName": "Example Shipping Co" }, { "EntID": 48230, "EntCode": "EXLOG", "EntName": "Example Logistics Ltd" } ], "RowsAffected": 2, "Scalar": null, "Identity": 0}| Field | Meaning |
|---|---|
EntID |
The entity’s ID. Read the entity with GetEntity. |
EntCode |
The entity’s code (Entity Code). |
EntName |
The entity’s name (Entity Name). |
When no entity was created or changed in the period, the answer has Code 0 and Info
No data found.

