Admitad
Admitad programmes and promo codes in your multi-network pipeline
Teams searching Admitad API often need offers across CIS and EU storefronts without maintaining a separate Admitad-only client. Connect Admitad in Feedico, then read firms and coupons through the same coupon API you use for CJ or Awin. See the unified affiliate API overview for the full multi-logo story.
Also unify
Who is this for?
Teams that monetize through Admitad and need the same engineering pattern as other affiliate sources.
How data flows
What you get with Feedico
Same list contract
Pagination and filters match your other network jobs.
Provider metadata
Filter Admitad rows when a surface should stay network-specific.
Less parser churn
Field mapping lives in Feedico when Admitad export shapes change.
Multi-network UX
One codebase for coupon sites, apps, and internal tools.
Connecting Admitad: credentials, endpoints, and what syncs
Authentication: OAuth client credentials: Feedico exchanges ID + secret for a short-lived bearer token. Secrets are encrypted at rest and never returned by the API.
What you enter in the dashboard
- Client ID
- Your Admitad application client ID.
- Client secret
- Application secret; stored encrypted.
- Website ID
- The ad space (website) the coupons belong to.
Admitad APIs Feedico calls
- GET /coupons/website/{websiteId}/?status=active
- Active coupons for your ad space.
- GET /banners/{campaignId}/?website={websiteId}
- Creatives per campaign when needed.
| Admitad object | Feedico row |
|---|---|
| Campaign | Firm row, provider admitad |
| Active coupon | Coupon row with code, dates, and regions |
- Only coupons with status=active are pulled, so expired Admitad codes drop out on the next sync.
About Admitad
Admitad is a global affiliate network connecting advertisers and publishers, with strong presence in Eastern Europe and international programmes. See admitad.com for official publisher resources and policies. www.admitad.com/. Admitad is independent third-party software; trademarks belong to their owner. We summarise public positioning only - confirm policies and programme rules on the vendor site.
How it works
- 1
Connect Admitad
Enter your Client ID, Client secret and Website ID in the dashboard - only for programmes you are approved on.
- 2
Sync & normalize
Feedico calls GET /coupons/website/{websiteId}/?status=active and GET /banners/{campaignId}/?website={websiteId}, then maps campaign and active coupon into normalized firm and coupon rows.
- 3
Call one API
Same list endpoints, pagination, and POST filters as your other connected providers.
- 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 (admitad).
{
"provider": "admitad",
"networkName": "Example Store EU",
"merchant": "Example Store",
"title": "15% off your order",
"code": "SAVE15",
"offerUrl": "https://…"
}Native integration vs Feedico
| Topic | Via Feedico | One-off native client |
|---|---|---|
| Schema alongside other networks | ✅ Shared | ❌ Fork per vendor |
| Auth & secrets in your app | ✅ One Feedico token | ⚠️ OAuth client credentials: Feedico exchanges ID + secret for a short-lived bearer token. |
| Admitad APIs to integrate | Handled in the sync layer | 2 (GET /coupons/website/{websiteId}/?status=active; GET /banners/{campaignId}/?website={websiteId}) |
| Schema drift from vendor updates | Absorbed in mapping | ❌ Your on-call |
| When native API is still right | - | ✅ Exclusive fields / edge workflows |
Why pair Admitad with a unified layer?
Admitad alone needs 3 credentials and its own auth scheme (OAuth client credentials: Feedico exchanges ID + secret for a short-lived bearer token). Most growth teams do not stop at one flagship programme source. When Admitad 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 company as Admitad?
- No. Admitad is an independent affiliate network. Feedico is separate integration software: you connect Admitad in our dashboard and read normalized list rows through Feedico's API.
- Do I still need Admitad programme approval?
- Yes. Feedico does not bypass Admitad enrollment or publisher policies. You must stay approved for the programmes you promote.
- Can I combine Admitad with CJ or Awin in one app?
- Yes. Filter by provider when a feature needs only Admitad rows, or consume blended lists when your UX shows multi-network deals.
- When should I use Admitad's native API directly?
- When you need Admitad-exclusive admin or reporting workflows. Feedico targets multi-network catalogue and coupon consumption in your product.
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.