Affiliate API
One API for affiliate programmes, merchants and coupons
This page is the engineering entry point: what to list, how pagination fits, and how automation attaches. For the bird's eye diagram and full provider list, start at unified affiliate API for both the architecture map and the multi-network consolidation story. Feedico maps firms (merchant / programme catalogue) and coupons (promotions) behind the same bearer token, pagination model, and normalized fields - the backbone of affiliate automation when you sync many programmes without bespoke cron clients. When your UI is code-first, add the coupon API lens; when editors think in modules and carousels, add the deal merchandising (same coupon rows) lens.
Who is this for?
Built for teams shipping affiliate-powered products - not one-off scrapers.
If you landed from affiliate marketing API, publisher API, or partner programme API searches - you want one contract for catalogue + promotions, not five proprietary SDKs.
How data flows
Upstream programmes stay theirs; Feedico is the abstraction your backend integrates with.
What you get
Unified merchant data
Normalized firms and programme context - one mental model whether the row came from CJ or Awin.
Coupon + deal rows
One contract for promotions alongside catalogue; pair with the coupon API and its deal merchandising section when you split landing pages.
Shared auth & pagination
Bearer token, page / pageSize, and POST filters - no per-network client spaghetti in your repo.
Network abstraction
Upstream schema drift and quirks are absorbed in Feedico; your consumer code stays stable when a network tweaks fields.
Your backend calls Feedico; Feedico talks to upstream platforms with your stored credentials and surfaces availableProviders so filters match reality.
Supported networks
Connect credentials in the dashboard for sources your account is approved for. Icons are favicons for recognition - trademarks belong to their owners.
How it works
Same through-line as the coupon API: networks → normalization → REST → your surfaces.
- 1
Affiliate networks
Live credentials and programme approvals at CJ, Awin, Impact, Partnerize, Admitad, TradeTracker, and more.
- 2
Normalization & sync
Feedico maps upstream feeds into firm and coupon tables on a plan-aware cadence - dashboard visibility, jobs, webhooks where enabled.
- 3
REST API
Versioned HTTPS JSON: list merchants, list coupons, filter by provider, paginate predictably.
- 4
Your app
Websites, mobile, extensions, internal tools - your cache and disclosure layer on top.
Illustrative merchant + coupons shape
Your integration typically calls firm and coupon list endpoints separately; this composite shows how a product screen might join them. Field names follow customer OpenAPI (provider, networkName, etc.). network below is a readable label; API responses use machine provider slugs.
{
"merchant": {
"name": "Nike",
"network": "CJ",
"provider": "cj_affiliate",
"networkName": "Nike US"
},
"coupons": [
{
"title": "10% Off",
"code": "SAVE10",
"offerUrl": "https://…"
}
]
}Feedico vs manual affiliate APIs
| Topic | Feedico | Manual APIs |
|---|---|---|
| One auth | ✅ | ❌ |
| Unified merchant model | ✅ | ❌ |
| Shared coupon schema | ✅ | ❌ |
| Multiple networks | ✅ One integration surface | ⚠️ Possible - but N times the maintenance |
Longer rationale: Feedico vs manual integrations.
Why this matters
Every affiliate network introduces a different integration surface: auth, pagination, field names, rate limits, and breaking changes on someone else's roadmap. That tax lands on your engineers and slows roadmap work that actually moves revenue. Feedico compresses that complexity into one predictable API contract for merchants and promotions - so you keep network relationships, delegate normalization and delivery, and ship product experiences faster.
When this page is the right fit
Choose this landing when you want a broad affiliate data API (catalogue + codes) under one mental model. If you only need promotions, start with the coupon API; if bulk ETL is the main job, read the coupon feed API and deal merchandising (coupon API).
Frequently asked questions
- Do I still need network approval?
- Yes. Feedico does not replace enrolment or compliance at each affiliate network. You connect your own credentials and must stay approved for the programmes you promote. Feedico normalizes and delivers data - it does not grant access to merchants you have not legitimately joined.
- Can I combine multiple affiliate networks?
- Yes. Connect multiple sources in the dashboard; firm and coupon list responses can include rows from every connected provider. Use filters such as provider and availableProviders metadata to segment or merge networks in one integration. See also the affiliate network API narrative for multi-network positioning.
- Does Feedico host affiliate links?
- Feedico stores and serves normalized programme, merchant, and promotion metadata (for example offer URLs returned by your connected integrations). You remain responsible for outbound tracking links, disclosures, and how click traffic is attributed in line with each network's policies and your own product terms.
- Is this an attribution SDK?
- No. Feedico focuses on data delivery - merchant/firm listings and coupon or deal rows - over HTTPS JSON. You implement click routing, conversion tracking, and attribution in ways each network allows; Feedico is not a drop-in measurement SDK.
- How are quotas handled?
- Customer API usage is metered: successful calls to account-scoped list endpoints count against your plan's monthly quota (UTC calendar month). When limits are exceeded, the API returns a documented error so you can backoff, cache, or upgrade. Exact numbers appear in plan copy and documentation.
Network-specific guides
Volume often clusters on a flagship source. If one network dominates your funnel today, pair this page with focused landings - then keep Feedico as the unified contract: CJ API, Awin API, Impact API.
You need programme approval and compliant use at each affiliate network. Feedico provides the integration layer - not a substitute for network terms.