Feedico
Impact.com (favicon)

Impact.com

Impact partnerships through the same JSON surface as your other networks

Builders searching an Impact APIpath often already rely on Impact's native tooling - yet still need consistent catalogue + coupon rows beside CJ or Awin in the same product surfaces. Feedico registers Impact as a provider and projects firms and coupons into the shared Feedico model. Positioning: unified affiliate API; operations-heavy pulls: coupon feed API.

Also unify

Who is this for?

Teams that monetize through Impact.com and need the same engineering pattern as other affiliate sources.

How data flows

What you get with Feedico

  • Impact rows in the shared envelope

    Offer and merchant context lands in the same list shape as other connected sources.

  • Less DTO sprawl

    Pause adding Impact-specific types next to Awin-specific types - consume one contract.

  • Agency-friendly onboarding

    New client portfolios pick up Impact alongside other logos without rewriting ingestion glue.

  • Escape hatch stays open

    Keep Impact-native APIs where you need exclusive depth; use Feedico for everyday multi-network UX.

Connecting Impact: credentials, endpoints, and what syncs

Authentication: HTTP Basic auth (Account SID + Auth Token) against api.impact.com. Secrets are encrypted at rest and never returned by the API.

What you enter in the dashboard

Account SID
Your Impact media partner account SID.
Auth Token
From Impact Settings → API; stored encrypted.

Impact APIs Feedico calls

GET /Mediapartners/{AccountSID}/Campaigns
Campaigns (brands) you partner with, paginated.
GET /Mediapartners/{AccountSID}/Ads
Ads, including promo-code ads, per campaign.
How Impact data maps to Feedico rows
Impact objectFeedico row
Campaign / advertiserFirm row, provider impact_com, with countries when set
Ad carrying a promo codeCoupon row
Tracking linkofferUrl on your /me lists
  • Pagination follows Impact's PageSize / Page parameters, so large accounts sync in batches.

About Impact.com

Impact.com markets a cloud partnership management platform spanning affiliates, creators, commerce media, and B2B relationships - headquartered in the United States with a global office footprint. It publishes first-party integration resources for brands and partners; Feedico is additive when your consumer product needs cross-network normalization. impact.com/. Impact.com is independent third-party software; trademarks belong to their owner. We summarise public positioning only - confirm policies and programme rules on the vendor site.

Relationship to Impact's own APIs

Impact publishes first-party APIs and docs for direct integrators. Feedico is additive when you want multi-network simplicity on the consuming side - not a replacement for Impact account administration, contracts, or specialised reporting. Confirm details on impact.com.

How it works

  1. 1

    Connect Impact.com

    Enter your Account SID and Auth Token in the dashboard - only for programmes you are approved on.

  2. 2

    Sync & normalize

    Feedico calls GET /Mediapartners/{AccountSID}/Campaigns and GET /Mediapartners/{AccountSID}/Ads, then maps campaign / advertiser, ad carrying a promo code and tracking link into normalized firm and coupon rows.

  3. 3

    Call one API

    Same list endpoints, pagination, and POST filters as your other connected providers.

  4. 4

    Ship product

    Websites, apps, extensions, or pipelines - one consumer path for every network.

Example row shape

Illustrative JSON - your integration uses customer OpenAPI field names. provider identifies the source (impact_com).

{
  "provider": "impact_com",
  "networkName": "Partner Brand US",
  "merchant": "Partner Brand",
  "title": "15% off your order",
  "code": "SAVE15",
  "offerUrl": "https://…"
}

Get Impact.com coupons with code

Once your Impact.com account is connected, every coupon comes from one endpoint: POST /api/v1/me/coupons with "provider": "impact_com". Leave providerout to get every connected network in the same format. Create a token under Account in the dashboard; each successful call counts toward your plan's monthly request quota.

curl
curl -sS -X POST "https://api.feedico.io/api/v1/me/coupons" \
  -H "Authorization: Bearer $FEEDICO_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"provider": "impact_com", "page": 1, "pageSize": 50}'
Node.js
// Node 18+ (built-in fetch): every active Impact.com coupon, page by page.
const token = process.env.FEEDICO_TOKEN;

async function fetchCoupons() {
  const all = [];
  for (let page = 1; ; page++) {
    const res = await fetch("https://api.feedico.io/api/v1/me/coupons", {
      method: "POST",
      headers: { Authorization: `Bearer ${token}`, "Content-Type": "application/json" },
      body: JSON.stringify({ provider: "impact_com", page, pageSize: 200 }),
    });
    if (res.status === 429) throw new Error("Monthly API quota reached");
    if (!res.ok) throw new Error(`HTTP ${res.status}`);
    const data = await res.json();
    all.push(...data.coupons);
    if (page * data.pageSize >= data.recordCount) break;
  }
  return all;
}

fetchCoupons().then((coupons) => {
  for (const c of coupons.filter((c) => c.code)) {
    console.log(c.networkName, c.code, c.title, c.endsAt);
  }
});
Python
# Python 3 + requests: every active Impact.com coupon, page by page.
import os
import requests

URL = "https://api.feedico.io/api/v1/me/coupons"
HEADERS = {"Authorization": f"Bearer {os.environ['FEEDICO_TOKEN']}"}

def fetch_coupons():
    page, rows = 1, []
    while True:
        r = requests.post(URL, headers=HEADERS, json={"provider": "impact_com", "page": page, "pageSize": 200}, timeout=30)
        r.raise_for_status()
        data = r.json()
        rows += data["coupons"]
        if page * data["pageSize"] >= data["recordCount"]:
            return rows
        page += 1

for c in fetch_coupons():
    if c.get("code"):
        print(c["networkName"], c["code"], c["title"], c["endsAt"])
PHP
<?php
// PHP 7.4+ with cURL: first page of active Impact.com coupons.
$ch = curl_init("https://api.feedico.io/api/v1/me/coupons");
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        "Authorization: Bearer " . getenv("FEEDICO_TOKEN"),
        "Content-Type: application/json",
    ],
    CURLOPT_POSTFIELDS => json_encode(["provider" => "impact_com", "page" => 1, "pageSize" => 50]),
]);
$data = json_decode(curl_exec($ch), true);
curl_close($ch);

foreach ($data["coupons"] as $c) {
    if (!empty($c["code"])) {
        echo "{$c["networkName"]}  {$c["code"]}  {$c["title"]}\n";
    }
}

Other filters: firmName (merchant name), q (search brand, title, or code), and includeInactive. Full schema in the API docs.

Native integration vs Feedico

Impact.com data: Feedico vs bespoke per-network client
TopicVia FeedicoOne-off native client
Schema alongside other networks✅ Shared❌ Fork per vendor
Auth & secrets in your app✅ One Feedico token⚠️ HTTP Basic auth (Account SID + Auth Token) against api.impact.com.
Impact.com APIs to integrateHandled in the sync layer2 (GET /Mediapartners/{AccountSID}/Campaigns; GET /Mediapartners/{AccountSID}/Ads)
Schema drift from vendor updatesAbsorbed in mapping❌ Your on-call
When native API is still right - ✅ Exclusive fields / edge workflows

Why pair Impact.com with a unified layer?

Impact.com alone needs 2 credentials and its own auth scheme (HTTP Basic auth (Account SID + Auth Token) against api.impact.com). Most growth teams do not stop at one flagship programme source. When Impact.com is one leg of a multi-network roadmap, maintaining parallel DTOs burns velocity. Feedico lets you keep the relationships that matter while consolidating what your product consumes day to day.

Frequently asked questions

Is Feedico the same as Impact.com?
No. Impact.com (Impact Tech, Inc.) operates the partnership automation platform. Feedico is separate integration software that connects to Impact with your credentials and maps rows into Feedico's shared list schema.
Do I still need Impact partnership approvals?
Yes. You remain subject to Impact contract terms and programme rules for every brand you promote. Feedico is a data delivery layer, not a substitute for partnership onboarding.
Should we drop Impact’s native APIs if we use Feedico?
Not necessarily. Many teams keep Impact-first-party APIs for deep partner workflows and use Feedico where product UX needs one JSON model across Impact, CJ, Awin, and more.
Who is this integration pattern for?
Publishers and agencies comparing Impact coupon or catalogue ingestion with other networks - especially when product, data, or SEO teams insist on a single schema.
How are Feedico API quotas enforced?
Metered monthly successful list calls per your Feedico plan (UTC). Plan documentation states caps; implement caching and backoff for high-volume polls.

Affiliate disclosure: some links on Feedico are affiliate links. We may earn a commission when you buy through them, at no extra cost to you. Publishers still need programme approval and compliant use at each affiliate network. Feedico provides the integration layer, not a substitute for network terms.

Related pages

Concept & comparisons