Changelog Sync: Keep a Video Site Fresh Without Re-Downloading Everything

The first import of a catalogue is a one-off. After that, re-reading every page to find what changed is the slowest, most expensive way to stay up to date. A changelog gives you only the differences.

How it works

curl -H "X-API-Key: $KEY" \
  "https://adultembed.com/api/changelog/?since=2026-10-01T00:00:00Z"

Each entry is an event — video_added, video_updated or video_deleted — with a timestamp. Process them in order, then store the newest timestamp as your next since.

A safe sync loop

1. Read your saved watermark (the last event time you processed).
2. Request the changelog since that time and walk every page.
3. Apply each event: create, update or unpublish.
4. Save the new watermark only after everything was applied.

Saving the watermark last means a crash in the middle simply replays a few events next time, instead of silently skipping them.

Handle deletions properly

Removed scenes matter as much as new ones. A video page that plays nothing is worse than no page: visitors bounce and search engines notice. When you receive video_deleted, unpublish the post and, if it ever had traffic, answer with a 410 so crawlers drop it quickly.

How often to run it

Every hour or two is plenty for most sites. Running it every minute does not make the catalogue grow faster; it just spends your request allowance.