Developers · Affiliate API · Coupon feed API · Deals JSON

One normalized REST API for affiliate merchants, coupon codes, and deal feeds

Instead of integrating multiple affiliate APIs separately, Feedico gives you one Bearer-token JSON contract for unified merchants, unified coupons, and affiliate network metadata - a true coupon aggregation API and affiliate data API behind HTTPS.

Connect multiple affiliate networks in one API. Instead of integrating CJ, Awin, Impact, and every other affiliate network API separately, Feedico exposes one normalized REST surface: Bearer-token JSON for merchant (firm) lists, coupon feeds, provider filters, and pagination - an affiliate data API and coupon aggregation API for publishers, agencies, and developers. Teams building deal sites, affiliate product catalogs, internal BI, or lightweight aggregators use the same pagination, filtering, and stable schema to ingest CJ, Awin, Impact-class programs and more - without maintaining bespoke adapters per network.

Read the docs hub Interactive API explorer (Scalar)Get a token - start free

Why developers use Feedico instead of raw network APIs

Raw affiliate network APIs differ in auth quirks, field names, pagination, throttling, and error semantics. Feedico's value is consolidation: ingest once from our affiliate merchant API and coupon feed API, then fan out to your CMS, data warehouse, or mobile apps.

✓One normalized schema for merchants and coupons
✓One Bearer auth system instead of per-network OAuth gymnastics
✓Consistent pagination (page, pageSize, recordCount) across lists
✓Provider filters without rebuilding joins in your code
✓Faster integration cycles for agencies shipping many clients
✓Reduced maintenance when networks change payloads

Supported affiliate networks (integrations)

Feedico connects publisher accounts to major networks so your affiliate API responses stay rich. Exact availability depends on your dashboard setup, but teams routinely wire CJ Affiliate, Awin, Impact, TradeTracker, Partnerize, Admitad, Takeads, Takedeals, and related programs. Larger program lists and SEO deep-pages for each network live on the homepage networks section and evolve as we expand coverage.

CJ Affiliate (Commission Junction)
Awin
Impact
TradeTracker
Partnerize
Admitad
Takeads
Takedeals

What you get in JSON

Unified merchant (firm) rows with display names, provider keys, website URLs, status, and coupon counts.
Normalized coupon objects with code, title, validity window, tracking URLs, and network linkage.
Coupon aggregation semantics through consistent list envelopes (record counts + paging).
Provider-aware filtering so one HTTP integration can segment CJ vs Awin vs Impact-class rows.

API capabilities

Cursor pagination
page / pageSize with recordCount totals - ideal for data sync jobs and incremental ETL.
Text & provider filters
firmName substring search plus provider keys such as cj_affiliate to narrow coupon feeds.
Bearer authentication
Simple Authorization headers for automation, scripts, and server-side workers.
Deterministic JSON
Stable field naming so your ORMs, SDKs, and serializers stay boring (in a good way).
Network normalization
One merchant / coupon schema regardless of upstream feed quirks.
HTTPS-only contracts
Ready for production apps, CI runners, and observability stacks.
Monthly quotas
Predictable plan-based limits with structured 429 responses when you need to upshift.
Automation hooks
Pair JSON lists with dashboard exports, desktop sync, or webhook-style delivery on eligible plans.
OPTIONS compatibility
CORS-friendly patterns for browser-side sandboxes when applicable.

Developer & publisher use cases

Topical clusters that pair naturally with an affiliate product API and coupon feed API landing page.

Build coupon and deal websites
Render fresh offer pages from JSON without scraping affiliate portals.
Sync affiliate merchants nightly
Page through firms, hydrate your CMS, and reconcile status changes automatically.
Launch deal aggregators & vertical directories
Blend multiple networks into one search experience with unified objects.
Power browser extensions & widgets
Ship lightweight clients that only need HTTPS + Bearer auth.
Feed WordPress affiliate stacks
Pair this API with the Feedico Sync plugin when you want no-code publishing.
Internal BI & finance tooling
Land coupons in a warehouse and join with your margin models.
Price comparison prototypes
Join affiliate merchant metadata with your catalog ingestion pipelines.
Agency multi-tenant rollouts
Clone the same integration per client with different tokens and dashboards.

WordPress coupon integration (no-code path)

Not every team wants raw HTTP. The same affiliate deals API token powers the official Feedico Sync WordPress plugin: scheduled imports, auto-import of merchants and coupons, Gutenberg blocks, and shortcodes - with Feedico acting as the multi-network backend source.

Sync affiliate coupons into WordPress on a timer
Import merchants as structured content for niche sites
Blend multiple network feeds without custom PHP adapters

Explore the WordPress integration →

Local affiliate ETL companion

Need a downloadable mirror? The Linux desktop client syncs the same normalized merchants and coupons into SQLite or MySQL for offline coupon databases and ops workflows.

Why teams choose Feedico lists

Single integration
One affiliate network API facade instead of bespoke adapters per program.
Normalized responses
Predictable merchant + coupon shapes for your deal feeds.
Production defaults
HTTPS-only, structured errors, automation-friendly POST list verbs.

Authentication, quotas, and resilience

Dashboard API tokens use the fdco_ prefix. Send Authorization: Bearer <token> on customer endpoints under /api/v1/me/. Browser session JWT routes (profile, password changes) are separate - the examples below target automation-style Bearer flows.

Lifecycle: rotate credentials through the dashboard, store them in a secret manager, and revoke stale tokens after cutover.

Scopes: customer tokens are account-scoped to your connected data - there are no fine-grained delegated scopes yet.

Rate limits: monthly quotas apply to successful list calls; upgrade paths unlock higher monthly ceilings (details in-app).

Retries: treat 429 as a throttle signal, backoff with jitter on 5xx, and keep POST bodies JSON-valid to avoid unnecessary errors.

Copy-paste requests & sample responses

Base URL for your deployment: https://feedico.io. Sample JSON illustrates envelope shapes - your live IDs and fields will differ. Full field matrices live in openapi-customer.yaml.

1. Verify token - GET /api/v1/me

Confirms the Bearer token and returns identifiers for automation logs.

Terminal - token check

curl -sS -X GET \
  "https://feedico.io/api/v1/me" \
  -H "Authorization: Bearer fdco_YOUR_TOKEN_HERE"

Sample JSON - identity envelope

{
  "ok": true,
  "userId": "7",
  "email": "you@example.com"
}

2. List merchants - POST /api/v1/me/networks

Paginated affiliate merchant API results with optional provider and firmName filters.

Minimal page of firms

curl -sS -X POST \
  "https://feedico.io/api/v1/me/networks" \
  -H "Authorization: Bearer fdco_YOUR_TOKEN_HERE" \
  -H "Content-Type: application/json" \
  -d '{"page":1,"pageSize":50}'

Filtered - provider + name

curl -sS -X POST \
  "https://feedico.io/api/v1/me/networks" \
  -H "Authorization: Bearer fdco_YOUR_TOKEN_HERE" \
  -H "Content-Type: application/json" \
  -d '{"page":1,"pageSize":50,"provider":"cj_affiliate","firmName":"example"}'

Sample JSON - merchant page (truncated)

{
  "ok": true,
  "recordCount": 1284,
  "page": 1,
  "pageSize": 50,
  "availableProviders": ["cj_affiliate", "awin_affiliate", "impact_com"],
  "networks": [
    {
      "id": "9204412",
      "provider": "cj_affiliate",
      "displayName": "Example Merchant  -  Shoes",
      "externalMerchantKey": "cj-merchant-123",
      "merchantWebsiteUrl": "https://example.com",
      "status": "active",
      "couponCount": 14
    }
  ]
}

3. List coupons - POST /api/v1/me/coupons

Query a coupon feed API with the same pagination helpers as merchants.

Coupons with text filter

curl -sS -X POST \
  "https://feedico.io/api/v1/me/coupons" \
  -H "Authorization: Bearer fdco_YOUR_TOKEN_HERE" \
  -H "Content-Type: application/json" \
  -d '{"page":1,"pageSize":25,"firmName":"summer"}'

Sample JSON - coupon page (truncated)

{
  "ok": true,
  "recordCount": 88432,
  "page": 1,
  "pageSize": 25,
  "availableProviders": ["cj_affiliate", "awin_affiliate"],
  "coupons": [
    {
      "id": "2642194",
      "networkId": "9204412",
      "networkName": "Example Merchant  -  Shoes",
      "provider": "cj_affiliate",
      "code": "SAVE20",
      "title": "20% off regular-priced styles",
      "endsAt": "2026-06-01T23:59:59Z",
      "offerUrl": "https://example.com/promo"
    }
  ]
}

Try requests in the interactive explorer

Long term, OpenAPI-powered explorers massively improve developer activation. Feedico hosts Scalar alongside the public API origin so you can exercise authenticated calls when you are ready (token required).

Open Scalar explorer Download openapi-customer.yaml Full openapi.yaml

Keep exploring the Feedico cluster

Internal links reinforce topical authority across pricing, education, and adjacent products.

Topics aligned with this API

Future editorial hubs that naturally cite an affiliate REST API landing page.

How to unify multiple affiliate APIs behind one facade
Building a coupon API aggregator vs CSV affiliate feeds
Normalizing affiliate merchant JSON from CJ, Awin, and Impact-class sources
Best API-first patterns for coupon websites & deal apps
Using affiliate HTTP APIs alongside WordPress
How to architect a deal site with JSON coupons instead of scrapers

Frequently asked questions

What is the Feedico REST API?Show

Feedico exposes a versioned HTTPS JSON API under /api/v1. Customer list endpoints live under /api/v1/me/* and return merchants (firms) and coupons from multiple affiliate programs through one affiliate API integration - the same normalized schema whether your data came from CJ Affiliate, Awin, Impact, or other supported sources.

How do I authenticate API requests?Show

Create an API token in your Feedico dashboard (fdco_… prefix). Send Authorization: Bearer <token> on GET /api/v1/me for a quick identity check and on POST /api/v1/me/networks and /api/v1/me/coupons. This is the same credential the WordPress plugin and many automation scripts use.

Is there token rotation or lifecycle guidance?Show

Treat fdco_ tokens like production secrets. Rotate by generating a new token in the dashboard, updating your workers, then revoking the old value. There are no per-route OAuth scopes today - the token is account-scoped for customer data list endpoints; keep it in a secret manager and avoid logging full strings.

Which networks and programs does the API cover?Show

You choose which integrations to connect in the dashboard (CJ Affiliate, Awin, Impact, TradeTracker, Partnerize, Admitad, Takeads / Takedeals, and others as Feedico adds them). The API returns normalized rows for your account - not raw network documents - so one client handles many programs.

Are there rate limits or quota errors?Show

Yes. Successful POST /api/v1/me/networks and /api/v1/me/coupons responses count toward a monthly Bearer-token quota tied to your plan (UTC calendar month). When exceeded you receive HTTP 429 with a structured monthly_api_limit payload. Back off exponentially, page with smaller pageSize if needed, and upgrade for higher throughput - exact limits appear in-app.

How should clients retry failures?Show

Use idempotent paging: if a request fails after partial processing in your own code, re-run the same page. On 429, honor cooldown and avoid tight loops. On 5xx, retry with jitter. Always send Content-Type: application/json on POST list routes.

Does Feedico support webhooks or CSV?Show

Webhooks are part of the broader Feedico automation story on eligible plans (see documentation). CSV export is available in complementary surfaces such as the web dashboard and Linux desktop client; the REST API itself is optimized for JSON coupon feeds and merchant lists.

Where is the full technical reference?Show

Start at /docs for the documentation hub. Machine-readable contracts live in /openapi.yaml and /openapi-customer.yaml, and an interactive Scalar explorer is hosted alongside the public API host for try-it-out requests when you are ready to deep-dive.

Create account - get an API token Full API documentation WordPress plugin (no-code)Linux desktop client

Why developers use Feedico instead of raw network APIs

Supported affiliate networks (integrations)

What you get in JSON

API capabilities

Cursor pagination

Text & provider filters

Bearer authentication

Deterministic JSON

Network normalization

HTTPS-only contracts

Monthly quotas

Automation hooks

OPTIONS compatibility

Developer & publisher use cases

Build coupon and deal websites

Sync affiliate merchants nightly

Launch deal aggregators & vertical directories

Power browser extensions & widgets

Feed WordPress affiliate stacks

Internal BI & finance tooling

Price comparison prototypes

Agency multi-tenant rollouts