Does Amazon Associates have an earnings API?
Short answer: no. And the two APIs you'll be pointed at are a dead endpoint and a different Amazon programme entirely.
There is no Amazon Associates earnings API
Amazon publishes no programmatic way to read your own affiliate commissions. Your numbers live in Associates Central and come out as an on-screen report or a CSV download, by hand.
Every API that turns up in search results for this question belongs to a different Amazon programme — and one of them no longer answers at all.
This question has a confusing answer because Amazon runs several unrelated programmes under one brand, each with its own API, and search results blend them together. Here is every Amazon API people mistake for an affiliate earnings endpoint.
Every Amazon API people think reports affiliate earnings
| API | Whose programme | Your commissions? | Status |
|---|---|---|---|
| Product Advertising API 5 | Amazon Associates | No — catalogue only | Deprecated · returns 403 |
| Creators API | Amazon Associates | No — catalogue only | Live · replaces PA-API 5 |
| Reporting API developer.amazon.com |
Amazon Appstore developers | No — app sales, not affiliate | Live · different programme |
| Selling Partner API | Amazon sellers | No — your own orders | Live · different programme |
| Associates reports | Amazon Associates | Yes — but not an API | Web UI + CSV export only |
The PA-API trap: it now returns 403
Most tutorials about "the Amazon affiliate API" mean PA-API 5. Two things are worth knowing before you spend a weekend on it.
First, it never returned earnings. Its operations — SearchItems, GetItems,
GetVariations, GetBrowseNodes — read Amazon's product catalogue so you can build
product listings. Nothing in it exposes what you were paid.
Amazon has deprecated PA-API 5 in favour of the Creators API, and calls to the old
endpoint come back as HTTP 403 Forbidden. The deprecation notice publishes no migration
deadline, so if you're following a guide written before this year, assume its code no longer runs.
The Creators API that replaces it is still catalogue-only: product data for publishers, influencers and affiliate partners. Commissions are not part of it.
The Reporting API trap: right data, wrong programme
Search for an Amazon earnings API and Google is likely to hand you
developer.amazon.com/docs/reports-promo/reporting-API. It describes exactly what you want:
sales reports, earnings and payments reports, subscription reports.
An Amazon earnings API
Sales, earnings, payments and subscription reports, pulled over REST with OAuth. On an
amazon.com domain, in Amazon's own developer docs.
The Amazon Appstore's API
Revenue reporting for Android apps distributed on Amazon's app store. Authenticates with Login with
Amazon and needs the scope adx_reporting::appstore:marketer.
An Associates account has no Appstore console, no security profile, and nothing to authenticate against. If you publish apps on the Amazon Appstore it's genuinely useful. For affiliate commissions it's a dead end — and it's the top result, which is why this keeps costing people an afternoon.
What actually works
Download the report by hand
In Associates Central, open Reports, choose the date range and export. The only route Amazon supports, and for most affiliates a two-minute job once a month. The Consolidated Summary of Earnings gives you the figure you'd otherwise chase with code.
Script the browser
With no endpoint to call, people automate the click instead: a headless browser signs in, requests the report, downloads the file. Public examples exist. It works, and it breaks — you're depending on a login flow and a page layout Amazon can change without warning, plus credentials parked in your automation. Worth it across many accounts; rarely worth it for one.
Record the monthly total
The unglamorous option is usually right. One number a month gives you an Amazon line that is exactly as accurate as the CSV, because it came from the CSV. The engineering for the previous option, spread over a year, buys you eleven minutes.
Why this matters beyond Amazon
Amazon Associates isn't the exception. A large share of what a solo operator earns comes from programmes with no earnings API at all: most affiliate networks, several ad networks, plenty of marketplaces. A dashboard built purely on integrations is structurally blind to that money — it reports the streams it can reach and quietly omits the rest, which makes the total wrong in the one direction that matters.
The fix isn't a better scraper. It's accepting that some sources get typed in, and building the reporting so a typed number and a synced number sit on the same screen and add up.
Amazon has no API. Count it anyway.
IncomeOS syncs the platforms that do have an API and lets you type the ones that don't as a monthly total, so Amazon stops being a hole in your numbers.
Try it free Or self-host it free — MIT, your own database. See my real numbers.