Developer documentation
Feedico documentation hub
Integration guides, network references, and API tools for teams building on affiliate and coupon data, one normalized REST API across CJ, Awin, Impact, Admitad, and more.
Last updated: June 27, 2026
Quick start
Three steps from sign-up to your first normalized coupon or merchant response.
- 1
Create an account
Sign up at feedico.io, verify your email, and connect the affiliate networks you already have programme access to.
Get started → - 2
Copy your API token
Open the dashboard and copy your Bearer token (fdco_…). Use it for server-side calls to /api/v1/me/* endpoints.
Open dashboard → - 3
Fetch normalized data
List merchants and coupons in one JSON schema. Cache responses, paginate, and wire webhooks on eligible plans.
API reference →
Integration guides
Narrative docs for architects and engineers, auth, pagination, caching, and product-specific patterns.
Affiliate API overview
Start hereStart here: what the API returns, the two ways to use it, integration steps and FAQs.
Read guide →Unified affiliate API
OverviewHow one REST surface aggregates merchants and coupons across multiple networks.
Read guide →Coupon API
CouponsPromo codes, titles, validity windows, and merchant context in normalized JSON.
Read guide →Affiliate API
PublishersProgrammes, merchants, and coupon listings for publisher catalogues and deal surfaces.
Read guide →Commerce data API
CommerceMerchant + product + offer in one commerce data infrastructure narrative for publishers and agents.
Read guide →Feedico MCP server
Open sourceMCP server for Claude, ChatGPT, Cursor and AI agents: coupons, deals and products with tracked partner links.
Read guide →Coupon API for AI agents
AIArchitecture guide for LLM shopping apps, tool-calling, and llms.txt discovery.
Read guide →Import CJ coupons to WordPress
WordPressStep-by-step mapping from Feedico JSON to WordPress posts, blocks, and cache keys.
Read guide →Build a coupon warehouse (ETL)
ETLBatch sync cadence, deduplication, and warehouse-friendly exports for BI teams.
Read guide →Webhook delta sync
WebhooksPush-style updates when catalogue rows change, reduce polling and stay within rate limits.
Read guide →Network guides
Orientation pages when your team searches for a specific affiliate network API, mapped to Feedico’s unified schema.
Commission Junction API orientation and Feedico mapping.
AwinAwin publisher API concepts and unified integration path.
ImpactImpact Radius / partner API notes for multi-network stacks.
AdmitadAdmitad programmes and coupon normalization.
TradeTrackerTradeTracker affiliate data via Feedico.
PartnerizePartnerize publisher integration overview.
Takeads / TakedealsTakeads network guide for coupon publishers.
Use cases
Product archetypes, each page covers architecture, compliance notes, and links to the right API surfaces.
Coupon websites
Deal sites, editorial stacks, and SEO-friendly offer pages.
Read guide →WordPress affiliate
Themes, plugins, and server-side API patterns for WP.
Read guide →Cashback apps
Rewards products with server-mediated affiliate data.
Read guide →Browser extensions
In-browser deal surfacing with compliant backend calls.
Read guide →API reference & developer tools
Machine-readable contracts and try-it-out tools live alongside narrative guides on this site.
- Auth: Bearer token
fdco_…from dashboard - Resources: coupons, merchants, network metadata
- Plans: webhooks & CSV export on eligible tiers
Interactive API reference
Scalar explorer on api.feedico.io, try endpoints with your Bearer token.
RapidAPI Hub listing
Gateway access for teams that prefer RapidAPI billing and SDKs.
openapi-customer.yaml
Machine-readable customer API contract for codegen and CI.
openapi.yaml
Full OpenAPI spec including internal and public routes.
Live demo
Browse sample coupon and merchant responses without wiring auth first.
Coupon data report
Freshness and catalogue stats to evaluate before production sync.
Source code downloads
Open-source plugins, example clients and the Postman collection, as .zip packages (MIT license unless stated in the package).
Feedico Sync (WordPress plugin)
Sync coupons and merchants into WordPress with blocks, shortcodes and optional AI enrichment (bring your own key).
Download .zip (316 KB) ↓Feedico MCP (AI coupon agent)
MCP server for Claude, ChatGPT, Cursor and AI agents: coupons, deals and products with tracked partner links.
Download .zip (27 KB) ↓Node.js API example
Minimal client for the Feedico API with pagination and filters.
Download .zip (7 KB) ↓Python API example
Fetch coupons and merchants from the Feedico API in Python.
Download .zip (7 KB) ↓PHP API example
Plain PHP client for the Feedico API.
Download .zip (9 KB) ↓C# / .NET API example
Typed .NET client and console sample for the Feedico API.
Download .zip (9 KB) ↓ETL starter (Python + SQLite)
Pull all coupons and merchants into a local warehouse table on a schedule; schema included.
Download .zip (5 KB) ↓Partner API: Postman + OpenAPI
Postman collection and OpenAPI spec for the Partner API (coupons, stores, products, links, link validation, reports) with tracked partner links.
Download .zip (9 KB) ↓Postman collection
Ready-to-import Postman collection for the Feedico API.
Download .zip (4 KB) ↓Verify downloads with SHA256SUMS.txt. Packages contain no credentials; add your own token in .env after copying .env.example (fdco_… for the API examples, a partner token fdcp_… for Feedico MCP).
Comparisons & deep dives
Research articles for teams evaluating affiliate API strategy before they commit engineering time.
Affiliate API
One REST contract for merchants, coupons, and multi-network sync.
Read guide →Schema normalization
CJ, Awin, Impact field mapping into one JSON contract.
Read guide →Commerce data API
How merchant, product, and offer objects fit one membership-backed stack.
Read guide →Best coupon APIs (2026)
Vendor comparison for publisher engineering teams.
Read guide →CJ vs Awin vs Impact
Network API differences before you unify.
Read guide →Feedico vs CouponAPI
When a unified multi-network layer fits.
Read guide →Feedico vs in-house ETL
Build vs buy for affiliate data pipelines.
Read guide →API fragmentation (2026)
Why publishers consolidate affiliate integrations.
Read guide →Frequently asked questions
- Where should I start with Feedico documentation?
- New publishers should read the Publisher integration hub, then the Coupon API or Affiliate API page depending on whether you primarily need promo codes or full merchant catalogues. Connect networks in the dashboard, copy your API token, and use the interactive reference on api.feedico.io.
- Does Feedico replace official CJ, Awin, or Impact APIs?
- No. You still need programme approval at each network. Feedico sits on your credentials and normalizes responses into one schema so your product code does not maintain a separate parser per network.
- How do I authenticate API requests?
- Use a Bearer token (fdco_…) from your Feedico dashboard. Call server-side from your backend or sync jobs, do not embed tokens in public front-end JavaScript.
- Is there OpenAPI or Swagger documentation?
- Yes. Download openapi-customer.yaml from this site or open the Scalar UI at api.feedico.io/api-docs. RapidAPI Hub also exposes a gateway for teams that prefer that workflow.
- Can I sync coupons into WordPress or a data warehouse?
- Yes. See the WordPress CJ import guide and the coupon warehouse ETL guide linked from this hub. Both patterns use the same normalized JSON whether you render pages or land rows in Snowflake, BigQuery, or Postgres.
- What rate limits and plans apply?
- Monthly API caps depend on your plan tier. Free accounts receive a starter quota; paid plans raise limits and unlock exports and webhooks. See the REST API product page for current tier details.
You need programme approval at each affiliate network. Feedico provides the integration layer, not a substitute for network terms or compliant tracking.