Events API


The Events API is provided by the Rakuten Advertising API Developer Portal. Visit the portal for a complete list of the APIs we offer.


The Events API allows for near real-time confirmation of a consumer transaction event that has completed on your advertiser partner's website. This API provides a full suite of Rakuten Advertising network data. Use the Events API to retrieve transaction confirmations of events that were completed on an advertiser-partner's website. It can add value to your business by:

  • Increasing the speed of your communication with your consumers, for example, if your business model provides consumers with shopping rewards via your website.
  • Providing near real-time visibility into performance so you can better optimize your ad spend and content placements.

If your site provides cash back or other rewards for members, or if you have a large team of content writers publishing frequently on your site, this tool may be very useful for you.


You can test the web service in the portal. Use your Publisher Dashboard login credentials to log in.


You need the API access token to make a successful call. View instructions for retrieving an API access token.

Technical Information

There are no required parameters for Events API requests. If you call Events with no parameters provided, default values will be applied, and you will receive your last 100 transactions by process date.

The Events API currently supports only JSON format.


The Events API should not be used for historical data because it will only collect and store the previous one to two weeks of data to enable u1 matching with most clicks. Historical reporting should be done from the Reporting Interface.

These transactions are meant to serve as an indicator of a transaction occurring, not as a way to determine or calculate commissions. For that purpose, use Signature Reconciliation Feed Reports.

Advertisers can, upon review, eliminate one or more of these transactions and report the finalized list via a batch upload.

Push or Postback Option

If you prefer to receive transaction events instead of fetching them via the Events API, we recommend you use the Postback API.

For More Information

Learn about the Events API’s methods, resources, parameters, and other details in the Developer Portal and the Events API Common Questions. If you have additional questions, contact Customer Support.

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.