Offer change log (offer-events) — what sellers get from it
What Allegro records in offer-events, how SalesAmplifier stores them, and how to tie changes to sales drops.
When sales on an offer drop, the first question is: what changed? An XLSX report shows outcomes (sales, visits) but not always the exact moment of a price, title, or status edit. That is what Allegro’s GET /sale/offer-events endpoint is for — a change journal for offers on your account.
What Allegro records
Offer-events are Allegro-side events (e.g. offer edits, status changes, end of sale). The API returns events from roughly the last 24 hours — that is Allegro’s window, not a SalesAmplifier limit. Longer history comes from regular sync (every 3 hours) and keeping earlier events in storage.
What you see in the app
After connecting your account (read-only OAuth):
- The worker pulls offer-events with a cursor — resuming from the last position.
- Events appear in Offer change events (
/offer-events). - Offer detail shows change history next to sales and visit metrics.
The API does not ship explicit “old value → new value” pairs in the event payload. Where possible, SalesAmplifier infers the diff from earlier offer snapshots — on the events list and offer detail. When there is no reference point, we show — instead of guessing.
How to connect this to sales
A typical workflow:
- Notice a drop in visits or sales on a chart or report.
- Open offer-events for the same period — was there a price, status, or end-of-sale change?
- If XLSX and API numbers disagree, check source reconciliation rather than assuming a sync bug.
Offer-events describe outcomes on Allegro’s side. Who clicked save in Sales Center and why — will later correlate with the read-only browser extension; API does not replace seller intent.
Scope and safety
- Integration is read-only — we never edit listings or campaigns.
- Data is for your seller account via OAuth — we do not scrape other sellers’ pages.
- Ads and visits still come mainly from XLSX — offer-events add offer change context.