Feedico

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. 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. 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. 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.

Network guides

Orientation pages when your team searches for a specific affiliate network API — mapped to Feedico’s unified schema.

Use cases

Product archetypes — each page covers architecture, compliance notes, and links to the right API surfaces.

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

Comparisons & deep dives

Research articles for teams evaluating affiliate API strategy before they commit engineering time.

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.