List assets by last edit time

When to use this endpoint

Use Assets_listByLastEdited when a synchronization process needs IDs first and will retrieve details separately.

Authentication and permissions

The request must authenticate with signed API-key fields or a logged-in CRM session. The handler requires login or an established tenant database context and performs no additional Asset-page or role-permission check unless the page says otherwise.

Every query and write uses the authenticated tenant’s tables. CRM1 and CRM2 may hide actions through client-side permissions that these collection routes do not repeat.

Parameters

Parameter	Type	Required	Description
`from`	Datetime string	Yes	Exact `YYYY-MM-DD HH:MM:SS` syntax. The comparison is inclusive (`>=`). Calendar validity is not checked beyond the regular expression.

Example request

$ids = FM_api('Assets_listByLastEdited', [
	'from' => '2026-09-30 12:00:00',
]);

Example response

["4821", "4828"]

Errors and unusual responses

Response	Condition
`{"error":"not logged in"}`	No authenticated tenant context is available. Invalid signed credentials can be rejected by the dispatcher before the handler runs.
`{"error":"missing \"from\" parameter, or parameter is in wrong format. should be \"yyyy-mm-dd hh:ii:ss\""}`	The value is absent or does not match the exact numeric shape.

Legacy application errors may be returned with HTTP 200. Check the decoded response for error, not only the HTTP status.

Behaviour and edge cases

Soft-deleted assets are excluded; archived and inactive assets are included.
There is no upper checkpoint, explicit ordering, pagination, or limit. Use an overlap/inclusive checkpoint strategy and deduplicate IDs.

See it in Fieldmotion

CRM1

No current direct CRM1 caller was found; it uses Assets_getNames for its name cache.

CRM2

No current direct CRM2 caller was found.

Related endpoints

Assets_getById can fetch the returned IDs in batches.
Assets_getNames includes compact identity fields and a final checkpoint.