Problem Solving

When doing Shopee Affiliate, developers often encounter the following issues:

• No easy-to-use public API to get commission by product
• Need to handle various URL formats (full link, short link…)
• Data changes continuously → need caching to optimize performance
• When the API fails → 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 about 3 hours to reduce latency and system load
• Providing a fallback when unable to fetch new data

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 valid → return immediately (dataSource: db)
   • If expired → call source API → save to DB → return (dataSource: api)

4. If the API fails:

   • If cached → return cache + warning
   • If not → 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 Shopee product link

👉 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 ~24 hours

👉 Recommendations:

• Use item_id instead of short link
• Implement additional caching on client/server 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, bot…)
  

📚 Purpose

The project is built for the purpose of:

• Learning and researching how to handle e-commerce data
• Referencing API architecture + caching + fallback
• Developing internal tools for analysis