Partnerize
Partnerize partnerships in the same Feedico pipeline as your other networks
Enterprise teams searching Partnerize API often still run CJ or Impact for long-tail retail. Connect Partnerize in Feedico, then surface promotions through the shared affiliate API and coupon API contracts. Map the full stack on the publisher hub.
Also unify
Who is this for?
Teams that monetize through Partnerize and need the same engineering pattern as other affiliate sources.
How data flows
What you get with Feedico
Enterprise + long-tail retail
Partnerize rows beside CJ/Impact without forked ingestion code.
Normalized promotion rows
Coupon objects share field names across providers.
Operator dashboard
Credentials and sync health alongside other integrations.
Compliance-friendly filtering
Provider metadata for audit trails in multi-network UIs.
Connecting Partnerize: credentials, endpoints, and what syncs
Authentication: HTTP Basic auth (Application Key + User API key) against api.partnerize.com. Secrets are encrypted at rest and never returned by the API.
What you enter in the dashboard
- Publisher (Partner) ID
- Your Partnerize publisher ID.
- User Application Key
- Application key from your Partnerize user settings.
- User API key
- User API key; stored encrypted.
Partnerize APIs Feedico calls
- GET /user/publisher/{id}/campaign/a.json
- Campaigns you are approved on.
- GET /user/publisher/{id}/campaign/{campaignId}/voucher.json
- Vouchers per campaign.
- GET /user/publisher/{id}/campaign/{campaignId}/creative.json
- Creatives per campaign.
| Partnerize object | Feedico row |
|---|---|
| Approved campaign | Firm row, provider partnerize, with countries |
| Voucher | Coupon row with code and validity |
- Vouchers are fetched per campaign, so sync time scales with the number of approved campaigns.
About Partnerize
Partnerize is an enterprise partnership platform for brands and publishers (part of Ascend). See partnerize.com for official programme documentation and publisher onboarding. partnerize.com/. Partnerize 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 Partnerize
Enter your Publisher (Partner) ID, User Application Key and User API key in the dashboard - only for programmes you are approved on.
- 2
Sync & normalize
Feedico calls GET /user/publisher/{id}/campaign/a.json, GET /user/publisher/{id}/campaign/{campaignId}/voucher.json and GET /user/publisher/{id}/campaign/{campaignId}/creative.json, then maps approved campaign and voucher 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 (partnerize).
{
"provider": "partnerize",
"networkName": "Example Brand US",
"merchant": "Example Brand",
"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 | ⚠️ HTTP Basic auth (Application Key + User API key) against api.partnerize.com. |
| Partnerize APIs to integrate | Handled in the sync layer | 3 (GET /user/publisher/{id}/campaign/a.json; GET /user/publisher/{id}/campaign/{campaignId}/voucher.json; GET /user/publisher/{id}/campaign/{campaignId}/creative.json) |
| Schema drift from vendor updates | Absorbed in mapping | ❌ Your on-call |
| When native API is still right | - | ✅ Exclusive fields / edge workflows |
Why pair Partnerize with a unified layer?
Partnerize alone needs 3 credentials and its own auth scheme (HTTP Basic auth (Application Key + User API key) against api.partnerize.com). Most growth teams do not stop at one flagship programme source. When Partnerize 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 Partnerize?
- No. Partnerize (part of Ascend) is an independent partnership platform. Feedico is a normalization layer for publishers who also run other networks.
- Do I still need Partnerize programme approval?
- Yes. Feedico does not replace Partnerize enrollment or compliance obligations.
- Can Partnerize coexist with CJ and Impact in one product?
- Yes. That is the primary Feedico use case: one client, many providers, consistent list contracts.
- When should I use Partnerize APIs directly?
- When you need Partnerize-specific partner management or reporting. Feedico focuses on multi-network catalogue consumption.
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.