REST · Bearer + x-api-key · 20 calls/min · api.awin.com · 5-service publisher + advertiser connector
Awin Offers API
→ TAOS Offer Library
Awin Link Builder API
→ TAOS Link Engine
Awin Performance APIs
→ TAOS Analytics + Signal Scoring
Awin Transaction data
→ TAOS Earnings + Loyalty
Awin Conversion API
→ TAOS Client/Advertiser mode only
Awin throttles to 20 calls/min per user. TAOS never depends on live-on-page API requests. All data is synced on schedule, cached locally, and read from Supabase.
Publisher mode = offers, links, performance, transactions. Advertiser mode = promotions, conversions, validation. These roles never mix in one workflow.
Awin says batches should go 10–60 seconds after the client-side request to stay within prioritization logic. Max 1000 orders per batch.
Intelligence layer — what to promote, when, and why · Generated 11:45:24 AM
Offer Sync
Scans awin_offers for heat score, vouchers, expiry dates
Performance Sync
Reads awin_performance for EPC, conversion rate, advertiser strength
Transaction Sync
Checks awin_transactions for commission trends and attribution
No signals yet
Sync offers and performance data from Awin to generate intelligence signals
Uses
Offer Sync · Performance Sync
Outputs
Promote this today · Voucher expires soon · Advertiser performing strongly
Uses
Offers + Categories + Markets · Performance by niche/persona
Outputs
Personalized product recommendations · Offer recommendations by persona
Uses
Generated deeplinks · Offer copy · Country/market routing
Outputs
Posts · Missions · Landing pages
Uses
Transaction ingestion · Click/sale data · Customer activity
Outputs
Points · "You could have earned" prompts · Customer-to-affiliate conversion
Uses
Conversion API · Batch Validation · Campaign reporting
Outputs
Client ROI · Affiliate payouts · Renewal prompts
Cookie & Data Preferences
TAOS uses cookies and similar technologies to operate the platform, analyse traffic, and personalise your experience. You can choose which cookies you accept. Essential cookies are always active.