Reports give you one row per day, per product, per Amazon marketplace. Each row tells you what activity drove that day: how many shoppers clicked, how many added to cart, how many bought, and how much commission moved. Two endpoints, same underlying data viewed from different sides:Documentation Index
Fetch the complete documentation index at: https://docs.archeraffiliates.com/llms.txt
Use this file to discover all available pages before exploring further.
GET /reports(Publisher API tab) — publisher view. Rows are scoped to links you created. Shows the commission you earned.GET /sellers/reports(Seller API tab) — seller view. Rows are scoped to brands you own. Shows the commission you paid out and acreatorcolumn telling you which publisher drove each row.
Filtering
Both endpoints accept:| Parameter | What it does |
|---|---|
start, end | Required date range (inclusive). YYYY-MM-DD or YYYYMMDD. |
marketplace | Restrict to one marketplace. Pass all or omit for every marketplace. |
asins | Comma-separated ASINs. |
brand_ids | Comma-separated brand ids — only useful if you have access to more than one. |
creators | Comma-separated creator identifiers (seller endpoint only). |
Currency
Sale amounts come back in the marketplace’s native currency. The row carries bothmarketplace and currency. No FX conversion is applied — if you
need a unified-currency aggregate, convert client-side.
Halo sales (seller view)
The seller report’ssales, conversions, and unitsSold include both
the linked product itself and any other items from the same brand
the shopper bought after clicking. This is the “brand halo” — Amazon
counts brand-wide value driven by the creator’s link, not just the one
product they linked to.
The publisher report only sees the linked product’s own attributed sales.
Paging
Reports use a cursor:next_cursor from the response and pass it back as cursor on the
next call. When next_cursor is null, you’ve seen everything.