Use case
Cashback & rewards apps
Unlike editorial sites that optimize for crawl and long-form pages, rewards products need coverage, trust, and backend rules: eligibility, ledgers, and disclosure copy at the moment of earn or burn. Users expect codes and boosts at checkout, not empty states because your CJ client broke. The Coupon API gives a single offer stream for mobile and web while you keep programme membership and payouts in your own compliance lane.
Product fit
- Browse & search - hydrate store and brand screens from normalized rows keyed the same way across networks.
- Campaign drops - schedule pulls when marketing runs short-lived boosts without rewriting adapters per source.
- Partner roadmap - onboard additional programmes in the dashboard instead of blocking app releases on a new OAuth client.
Backend-first integration
Ship a thin mobile client that talks to your API, not raw affiliate endpoints. Your service owns caching, personalization, and which subsets of coupons are eligible for a given user segment - then calls Feedico behind the scenes with a single integration pattern.
Deals beyond coupons
When your UX mixes percent-off promos with broader commerce events, pair this page's mental model with the deal feed API and the unified surface described under unified affiliate API.
How to build a cashback or rewards feed with Feedico
Connect the networks your members shop
Add CJ, Awin, Impact or the other supported networks in the dashboard with your own credentials.
Sync merchants and map them to your store list
Use externalMerchantKey plus provider as the stable key between Feedico rows and the stores in your app.
Pull offers on a schedule, server-side
Call the coupon list endpoints from your backend with pagination and cache the result; never ship the API token to the mobile app.
Show codes and deals with freshness
Render code for typed vouchers, fall back to title-only deals when code is null, and hide rows once endsAt has passed.
Route clicks through your own tracking
Use offerUrl for the outbound link and keep your cashback attribution and disclosures on your side.
Coupon fields you will use
| Field | How to use it |
|---|---|
| externalMerchantKey | Stable merchant key from the network; use it to join coupons to your store pages. |
| provider | Network slug (cj_affiliate, awin_affiliate, impact_com, …) for filtering and grouping. |
| code | Shopper-typed promo code, or null for title-only deals. |
| title | Offer headline as the network publishes it. |
| endsAt | End of the validity window; hide or archive the offer after it passes. |
| offerUrl | Your tracked link for the offer (account lists only). |
| fetchedAt | When Feedico last saw the row; show freshness from it. |
Full schema in the documentation; request examples on the affiliate API quickstart.
Frequently asked questions
- Does Feedico replace our ledger or redemption flow?
- No. Feedico supplies normalized offer and coupon metadata your app can surface in browse and search flows. Your wallet, ledger, and payout logic stay in your product.
- Can we show only certain merchants or networks?
- Use list filters such as provider and your own allowlists keyed off normalized merchant or programme identifiers. Combine multiple connected networks when your compliance model allows.
- How should mobile clients handle rate limits?
- Prefer server-side aggregation: your backend calls Feedico on a schedule or on demand with caching, not every tap from the device. Plans meter successful list calls per UTC month - design backoff and cache headers accordingly.
Affiliate disclosure: some links on Feedico are affiliate links. We may earn a commission when you buy through them, at no extra cost to you. Publishers still need programme approval and compliant use at each affiliate network. Feedico provides the integration layer, not a substitute for network terms.
Related pages
Ready to try it on your own networks?
Free plan, no credit card. Or start from the ready catalog with the Partner Program.