The ShareASale API stops working
ShareASale API
Stopped working
On October 6, 2025, the ShareASale API host api.shareasale.com stopped working following the closure of the platform. Requests sent to the API fail, and previously stored records such as payment statements can no longer be accessed or retrieved.
What to use instead of these calls
Switch to the Awin API at api.awin.com using an Awin OAuth2 user token, using endpoints such as GET /advertisers/{advertiserId}/transactions/ for transactions and GET /advertisers/{advertiserId}/reports/publisher for performance. This transition requires more than updating an identifier, as programs moved to Awin accounts, paths and formats differ, and some calls have no exact match.
ShareASale programs moved to Awin accounts: the Awin API needs a new token and its paths and formats differ, with no exact match for some ShareASale calls.
In ShareASale API's words
Payment statements were available on the ShareASale platform prior to its closure on October 6th. Unfortunately, since the platform has been closed, payment statements can no longer be accessed or retrieved.
Facts
- API
- ShareASale API
api.shareasale.com - Kind
- Endpoint removal
- Takes effect
- October 6, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against ShareASale API's own pages
Questions
When does this change take effect?
Calls to these calls on ShareASale API stopped working on October 6, 2025.
What happens to calls after October 6, 2025?
They have failed since October 6, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.