Every affiliate network. One API.

Publishers rarely work with a single affiliate network. CJ, Awin, Impact, Partnerize, Admitad, TradeTracker and others each have different APIs, authentication, and field names. An aggregator normalizes them into one schema so coupon sites, cashback apps, and extensions integrate once instead of once per network.

Affiliate data sits next to credentials for major networks, so we treat that responsibility seriously. Highlights below; full detail is covered during onboarding and in our Privacy Policy.

• HTTPS (TLS) for dashboard, customer API, and webhook delivery.
• Encryption at rest for upstream network credentials; API responses never echo raw secrets.
• Per-tenant API isolation - tokens and affiliate IDs are scoped so stacks cannot cross-contaminate.
• Least-privilege access patterns for automation workers connecting to partner APIs.
• GDPR-aware workflows: DPA available, documented subprocessors, and data subject tooling for regulated teams.
• Token hygiene guidance (rotation, storage in vaults) covered in integration docs.

Feedico is a B2B affiliate data platform that aggregates coupon, deal, and merchant information from multiple affiliate networks (including CJ Affiliate, Awin, Impact, Partnerize, Admitad, and TradeTracker) into one normalized API and dashboard. Publishers and software teams use it to avoid building and maintaining separate integrations for every network. For a fuller definition - including how Feedico differs from unrelated companies that may share a similar name - see https://feedico.io/what-is-feedico.

Feedico currently supports CJ Affiliate (Commission Junction), Awin, Impact, Partnerize, Admitad, TradeTracker, and Takeads. We add networks based on customer demand. Contact us if you need a specific integration prioritized.

Each network exposes different authentication, pagination, field names, and rate limits. Feedico absorbs that complexity: you get consistent resources (for example coupons and merchants), predictable filtering, and optional webhooks. Your team ships features instead of maintaining five different client libraries.

Yes. Many customers call our API on a schedule and persist results in their own database for full control and offline analytics. We recommend a short-lived cache or replica close to your app for low latency while keeping Feedico as the source of truth for freshness.

Networks often require clicks to originate from your approved domains. Feedico supports configuration patterns such as server-side link assembly, tracked redirects, or documented client-side templates, so you can match each program’s expectations. Details are covered in integration guides during onboarding.

Update frequency depends on your plan and each network’s policies. Typical configurations range from hourly to more frequent intervals for high-volume catalogs. We use delta-style pulls where networks support them to reduce payload size and stay within rate limits.

Yes. You can receive notifications when relevant data changes, or use cursor- or timestamp-based APIs to fetch only what changed since your last successful sync, which reduces bandwidth and processing on your side.

The primary interface is versioned JSON over HTTPS (REST). Responses use consistent field names for coupons, merchants, networks, and metadata. CSV or bulk exports may be offered for operational workflows; ask during enterprise evaluation.

No. Starter is aimed at individual sites and small teams that want reliable multi-network data without hiring a full integration squad. Starter includes limited outbound webhooks (monthly and daily caps); Pro and Business add higher scale and throughput. Enterprise (custom) covers dedicated capacity, white-label, and bespoke SLAs. Large publishers evaluating feed provenance should read our guide on how to verify affiliate coupon feeds at /best-coupon-apis-for-affiliate-publishers#feed-verification.

Starter lists at $15.99 per month at public rates. In the account dashboard you can place orders with prepaid terms (3, 6, or 12 months) that apply tier discounts on the full upfront total.

Create a free account, connect your networks in the dashboard, and issue an API token under Account. Paid plans raise monthly API caps; see /pricing for per-plan request limits.

Traffic uses TLS. Credentials for upstream networks are stored encrypted and scoped per customer. We design for least-privilege access and can provide a DPA for GDPR-regulated teams. Exact subprocessors and regions are documented during enterprise onboarding.

Normalization maps heterogeneous network payloads into one Feedico schema - consistent merchant keys, coupon fields, and pagination - so your code paths stay stable even when CJ, Awin, or Impact adjust their JSON. It is the core of our affiliate API aggregator value.

Customer REST traffic to /api/v1/me/* is metered per plan on a UTC calendar month (successful list responses count). Free tiers are capped for exploration; Starter, Pro, and Business unlock higher monthly ceilings - exact numbers appear in-app when you connect a token.

Yes. The Feedico Sync WordPress affiliate coupon plugin imports merchants and coupons, supports blocks/shortcodes, and keeps offers refreshed on a schedule. See the WordPress product page for positioning and technical notes: https://feedico.io/product/wordpress.

Use the Linux desktop client to mirror normalized merchants and coupons into SQLite or MySQL for internal analytics. Fresh sync still needs network access to Feedico, but local browsing and exports work offline: https://feedico.io/product/linux.

JSON is the primary automation interface; complementary surfaces (dashboard exports, desktop client) support CSV for editorial and BI handoffs depending on your workflow.

Reference documentation and OpenAPI exports are available from the docs hub and api.feedico.io; we expand guides and examples as endpoints evolve.