Problem Solved

When working with Shopee Affiliate, developers often encounter the following issues:

• No easy-to-use public API to retrieve commission per product

• Need to handle multiple different URL formats (full link, short link…)

• Data changes continuously → caching is needed to optimize performance

• When the API errors → no fallback

This API addresses the above issues by:

• Standardizing input (item_id or URL)

• Returning pre-processed data (price, commission, stats…)

• Caching data for ~24 hours to reduce latency and load on the system

• Having a fallback when new data cannot be fetched

How It Works (Architecture)

Processing Flow:

1. Receive request (item_id or url)

2. Extract item_id from URL (if needed)

3. Check cache database:

   • If still valid → return immediately (dataSource: db)

   • If expired → call source API → save to DB → return (dataSource: api)

4. If the API fails:

   • Has cache → return cache + warning

   • None → return fallback data

🚀 How to Use

Base URL

https://data.addlivetag.com/product-data/product-data.php

Method

• 
  GET / POST
  

Params item_id

Param Required Optional

Description Product ID

Params url

Param Required Optional

Description Link to Shopee product

👉 At least 1 of the 2 params is required

📦 Example Request

GET https://data.addlivetag.com/product-data/product-data.php?item_id=1589295236

📥 Example Response

{
  "status": "success",
  "productInfo": {
    "itemId": 1589295236,
    "productName": "Men's and Women's Sweater...",
    "price": 122200,
    "sales": 990,
    "rating": 4.8,
    "commission": 21996,
    "sellerComFinal": 16497,
    "shopeeComFinal": 5499,
    "dataSource": "db"
  }
}

⚡ Performance & Rate Limit

• API source: ~300 requests/minute

• Cache database: ~2000 requests/minute

• Cached data for ~24 hours

👉 Recommendations:

• Use item_id instead of short link

• Additional cache on the client/server side if building for production
  

🧪 Use Cases

• Tool for checking product commissions

• Dashboard for analyzing trending products

• Affiliate product picker for KOL/KOC

• Internal tools (like Riokupon, CMS, bots…)
  

📚 Purpose of Use

The project is built for the purpose of:

• Learning and researching how to handle e-commerce data

• Referencing API + caching + fallback architecture

• Developing internal tools for analysis