API: /documents/search returns stale lastModified / lastModifiedUserId

Question

Hi Lucid support,

We're using the Lucid API to track document changes across our organisation. We've found a discrepancy between what /documents/search returns and what the document version history shows in the web UI.

Here an example:

API response (/documents/search, polled 2026-06-26):
{
"documentId": "9eda633c-0916-4916-b912-a4db8417649a",
"lastModified": "2026-05-22T11:13:03Z",
"lastModifiedUserId": XXX365177
}

Web UI version history shows a newer version:
- Current version: 2026-05-29 11:19 PM — user XXX887201
- Previous: 2026-05-22 1:13 PM — user XXX365177 ← this is what the API returns

The API is returning the May 22 edit, not the May 29 current version.

Questions:
1. Does /documents/search only reflect certain save types (e.g. explicit saves vs. auto-saves)?
2. Is there a known propagation delay between a document edit and it appearing?
3. Is there an alternative endpoint that reliably returns the true current lastModified user?

Thanks
Tobi

Caden E · Answer

Hi Tobi,Great question. You’re correct that the API endpoint only reflects certain save types.Certain actions on a document, such as replying to a comment thread, trigger what we might call “silent” saves, since they don’t directly affect the document’s contents. The document version history shows these silent saves, but the set of saves that can be returned by the API does not.There isn’t an API endpoint that returns info about silent saves.

Create an account in the community

Log in to the community

Scanning file for viruses.

This file cannot be downloaded