One coupon API. Every network you already run.

Performance, scale & operations

API buyers care about predictable cost curves. Feedico exposes list endpoints with explicit pagination, documented pageSize caps, and plan-based monthly successful-call quotas so you can model spend. Sync frequency ties to your tier: fresher data when your UX demands it. Where enabled, webhooks reduce pure polling pressure; your edge cache still controls tail latency for public readers.

Example coupon payload

Illustrative JSON - field names align with our customer OpenAPI (provider, networkName, offerUrl, etc.). network below is a human label for the reader; responses use provider (cj_affiliate, …).

{
  "network": "CJ",
  "provider": "cj_affiliate",
  "merchant": "Nike",
  "networkName": "Nike US",
  "title": "10% off orders",
  "code": "SAVE10",
  "startsAt": "2026-05-01T00:00:00.000Z",
  "expiresAt": "2026-06-01T23:59:59.000Z",
  "offerUrl": "https://…"
}

Frequently asked questions

What is a coupon API?

A coupon API returns promo codes, titles, eligibility windows, and merchant context as structured JSON over HTTPS. Feedico's coupon API normalizes rows from CJ, Awin, Impact, and other networks into one listing contract for apps, sites, and ETL pipelines.

What is a unified coupon API?

A unified coupon API is a multi-network coupon listing contract: one bearer token, one JSON shape, and promo codes from every affiliate programme you connect. Feedico's /coupon-api endpoints are that unified coupon API; /unified-affiliate-api is the broader pillar for merchants, programmes, and coupons together.

Is Feedico a CouponAPI / couponapi alternative?

Teams searching couponapi or CouponAPI often want a single HTTP surface for codes. Feedico is a bring-your-own-network coupon API: you connect approved CJ, Awin, Impact (and other) credentials; we normalize and deliver. Compare philosophies on Feedico vs CouponAPI.

What is a coupon feed API?

A coupon feed API is the same listing contract used as a scheduled feed: page through coupons, persist slices, and refresh warehouses or CMS caches. Feedico's coupon feed API is not a separate product URL: it is the coupon list endpoints plus optional webhooks.

What are affiliate coupon feeds?

Affiliate coupon feeds are continuously refreshed streams of promo codes and voucher metadata from connected affiliate programmes. Feedico exposes them through list endpoints and a public live coupon feed sandbox so publishers can preview coverage before production coupon API integration.

What are coupon integrations?

Coupon integrations are the engineering patterns that wire a coupon API into WordPress, cashback apps, browser extensions, or data warehouses. Feedico supports coupon integrations through one bearer token: server-side fetch, pagination, and normalized fields, instead of bespoke clients per network.

Do I still need affiliate approval?

Yes. Feedico does not replace enrolment or compliance at each 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.

Does Feedico host affiliate links?

Feedico stores and serves normalized coupon and programme 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 site terms.

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 are shown in plan copy and documentation.

Can I use multiple networks together?

Yes. Connect multiple sources in the dashboard; responses can include rows from every connected provider. Filters such as provider and availableProviders metadata let you segment or combine networks in one integration.

Does Feedico normalize coupon fields?

Yes. Upstream networks use different shapes and field names; Feedico maps them into a consistent coupon listing model (titles, codes, windows, merchant keys, offer URLs, provider identity, etc.) so your application code stays stable.

Is the HTTPS listing different for ETL than for a customer-facing app?

No. Product UX, cron workers, warehouse loaders, and cache warmers all call the same account-scoped list contract. Use documented pagination until a page is empty, then store deltas in your own database. Plans still meter successful list calls per UTC month.

Can editors reuse the same rows for deals, carousels, or hero modules?

Yes. Flash promos, partner offers, and code-based savings map into the same normalized coupon model. Merchandising is mostly how you frame content in CMS or mobile UI; you do not need a second integration for deal strips if you already consume coupon lists.