Sales, commission and traffic for your links
See how your Archer links are performing — sales, commission, clicks and conversions — broken down by day, product and Amazon marketplace.
How rows are organised
You get one row for every combination of day, product and marketplace one of your links drove activity for. Each row carries its own marketplace and currency.
Date range
start and end are required. Either format works:
2026-05-01 or 20260501. Both ends are inclusive.
Marketplace
Reports cover a single Amazon marketplace per request. Pass either
marketplace=amazon.co.uk or the equivalent geo=UK (country code). If
both are passed, geo wins. Defaults to amazon.com (US) when neither
is supplied. marketplace=all is no longer supported.
See the Reporting concept for the full geo-to-marketplace mapping.
What’s in the numbers
Sales, conversions, add-to-carts and detail page views include
both the linked product itself and any other items from the same brand the
shopper bought after clicking — that’s how Amazon’s affiliate program
credits publishers. The numbers are returned in the marketplace’s native
currency. No currency conversion is applied; the row’s currency field
tells you which one it is.
Clicks are link-level — don’t sum them
Amazon reports clicks per ad group, per day, not per product: a click happens
on your link before the shopper reaches any particular product. Every Archer
link is backed by exactly one ad group, so that figure is your link’s daily
click count. Rows are per-product, so we repeat it on every product row
sharing that date + link.id.
Summing the clicks column therefore double-counts — a link that sold five
ASINs on one day produces five rows each carrying that day’s full click count.
Deduplicate on date + link.id and take the value once per group. Every
other metric is genuinely per-product and sums correctly.
Rows where a link got clicks but drove no attributed sales come back with
asin null and zero sales. Those clicks are real — include them.
See the Reporting concept for a worked example.
Paging through results
Use limit to control page size (1–500, default 100). For the next page,
take next_cursor from the response and pass it back as cursor. When
next_cursor comes back null, you’ve seen everything.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Query Parameters
First day of the report (inclusive). Use YYYY-MM-DD or YYYYMMDD.
Last day of the report (inclusive). Use YYYY-MM-DD or YYYYMMDD.
Amazon marketplace to report on — e.g. amazon.com, amazon.co.uk, amazon.de. Defaults to amazon.com when neither marketplace nor geo is supplied. Only one marketplace per request — all is not supported.
Two-letter country code for the marketplace, e.g. US, UK, DE. Alternative to marketplace; if both are supplied geo wins. See the Reporting concept for the full geo→marketplace mapping.
Limit results to one or more products by ASIN. Separate multiple ASINs with commas.
Limit results to specific links by their Archer link id. Separate multiple ids with commas.
Limit results to one or more brands. Separate multiple ids with commas.
How many rows to return per page (1–500). Defaults to 100.
1 <= x <= 500Use next_cursor from the previous response. Leave blank for the first page.
Response
Successful Response
The response from GET /reports.
Total rows matching your filters across every page.
Rows in this page.
The performance rows for this page.
Pass this back as cursor to fetch the next page. Null when you're on the last page.