Skip to content

docs(api): clarify synced_at semantics (1970-01-01 sentinel) #2331

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MikaKerman wants to merge 1 commit into
base: docs
Choose a base branch
from
Open

docs(api): clarify synced_at semantics (1970-01-01 sentinel) #2331

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/api/incremental-sync.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,17 @@ curl -H "Authorization: Bearer $ELEMENTARY_TOKEN" \

Timestamps are UTC ISO-8601.

<Note>
**What `synced_at` means.** `synced_at` marks when an object was **created or
last changed** in Elementary — not when it was last *seen*. Unchanged objects
keep their existing `synced_at`, and some objects that predate this field may
show a `1970-01-01T00:00:00` placeholder. This is expected and safe for
incremental loading: every object is returned by the initial full scan
(regardless of `synced_at`), and any later change gives it a fresh `synced_at`,
so it reappears in the `synced_since` feed. Treat `synced_at` as a change
marker for driving upserts, not as an absolute "last refreshed" timestamp.
</Note>

## Recommended loop

1. Store the wall-clock time `T` when you start a sync.
Expand Down
Loading