Pepperjam Integration Guide: Why It’s Now Ascend by Partnerize

Pepperjam doesn’t exist anymore in the form most search results describe. Pepperjam is now Partnerize in every practical sense, a legacy publisher API and a separate core Partnerize system, authenticated with its own credential pair, are what’s left running under the old name. If you’re trying to build one today, the honest first step is figuring out which of those two systems the advertiser you care about actually sits on, because the wrong guess costs you a rebuild.

Is Pepperjam Still an Independent Network? #

No. Pepperjam is now Partnerize. Partnerize acquired Pepperjam in July 2020, and it now operates as Ascend by Partnerize. Two separate API systems still exist under that umbrella today: the legacy ascend by partnerize api and core Partnerize’s own API, authenticated differently, and a pepperjam integration built without knowing which one you need is the most common way this project goes wrong.

READ THIS BEFORE ANYTHING ELSE Pepperjam no longer exists as an independent affiliate network. Partnerize acquired Pepperjam on July 29, 2020, and the network has since been rebranded “Ascend by Partnerize.” The old advertiser login at pepperjamnetwork.com is no longer the standard access point. Current accounts log in at console.partnerize.com, though the legacy platform itself is still reachable at ascend.pepperjam.com for API key management, which is a real source of confusion worth flagging to your team up front.

What Is Ascend by Partnerize Today? #

At the time of acquisition, Pepperjam served roughly 950 brands and 4,000 affiliate partners, meaningfully smaller than CJ, Awin, or Rakuten, and positioned more toward direct-to-consumer and subscription brands than mass retail. Post-acquisition, the combined Partnerize + Pepperjam business serves over 1,750 enterprise and midmarket clients globally. Partnerize’s own positioning skews toward larger managed programs rather than open self-serve individual publisher signup, which is a meaningful difference from how CJ, Rakuten, and Awin operate. If you’re weighing Pepperjam against other options at the network level, our piece on building a profitable affiliate network is useful background on how these programs are structured generally.

Why Are There Two Separate Technical Systems? #

THE DETAIL THAT WILL ACTUALLY TRIP UP YOUR INTEGRATION Even after the brand merger, Pepperjam/Ascend and core Partnerize run on two distinct API systems as of this writing. The former Pepperjam side still has its own Publisher API, reachable through the legacy ascend.pepperjam.com domain, authenticated with a simple ascend publisher api key generated under Resources → API Keys. Core Partnerize runs a separate REST API at api.partnerize.com, authenticated with a partnerize application key user api key pair (sent as headers or as Basic Auth credentials). Which one you need depends on whether the specific advertiser program you’re integrating with sits on the legacy Ascend/Pepperjam side or the core Partnerize platform. Check this before assuming one API covers both.

Ascend (Legacy Pepperjam) API and Your Ascend Publisher API Key #

• Log into Ascend, then navigate to Resources → API Keys (reachable via ascend.pepperjam.com/affiliate/api/) to generate your ascend publisher api key.
• Authentication for this side is that key plus your account username and password, depending on the specific endpoint.
• This is what most third-party reporting tools (Affluent, Strackr) currently document when they reference “Pepperjam” or “Ascend” as a data source, via the ascend by partnerize api rather than core Partnerize.

Core Partnerize API and the Partnerize Application Key User API Key Pair #

• Base URL is api.partnerize.com. Authentication is your partnerize application key user api key pair, generated from your account settings.
• A representative request: GET /network with the header Authorization: Basic {token} returns the networks your account has access to.
• Separate Brand and Partner API surfaces exist: the Brand API lets an advertiser manage and approve partners programmatically; the Partner API is the side a publisher (your cashback platform) would use to pull performance and generate links.

How Does Ascend / Partnerize Data Map to a Cashback Wallet? #

Because a pepperjam integration can sit on either of two systems, the wallet mapping has to account for both, and confirming which side a given advertiser is on before you model its data is the real work here.

System	Auth model	What this means for your wallet design
Ascend (legacy Pepperjam)	Ascend publisher api key + credentials	Model against whatever status fields the legacy Publisher API returns, confirm exact terminology with your account contact, since it isn’t fully documented publicly
Core Partnerize	Partnerize application key user api key pair	Network, Brand and Partner API objects follow Partnerize’s own reporting model. Confirm field-level detail directly rather than assuming parity with Ascend

In both cases, the safe default is the same one that applies across affiliate networks generally: hold withdrawable status behind a confirmed or locked state, never behind the first record of a tracked action, and confirm the exact status vocabulary for whichever system your advertiser sits on before you finalize the ledger schema.

NOT SURE WHICH API YOUR ADVERTISER USES?Our Pepperjam integration services cover both legacy and current authentication setups. Tell us the advertiser and we’ll tell you which system.→  Talk to our integration team

What Does Pepperjam / Ascend Publisher Approval Require? #

Because Partnerize positions toward managed enterprise and midmarket relationships rather than pure self-serve signup, expect more direct account-management involvement than with CJ, Rakuten, or Awin, particularly for larger programs. Individual advertiser approval still follows the same general pattern as other networks: each brand reviews and approves publishers into its own program. Our general guide to affiliate network approval covers what that review typically looks for.

What Are Ascend by Partnerize’s Payout Terms? #

The following payout terms are documented from the pre-acquisition Pepperjam network and may not reflect current Ascend by Partnerize terms exactly. Confirm directly with your account contact before relying on these figures for financial planning:

• Historical minimum payout threshold: $25.
• Historical payment schedule: twice monthly, on the 1st and 15th.
• Historical payment methods: PayPal, direct deposit, or check.

Under core Partnerize, publisher payouts are generally described as self-billed withdrawals released as advertiser funds clear, with frequency varying by program rather than a single fixed network-wide schedule.

Current-account details, payout history, and program status all live in the Partnerize console rather than the old Pepperjam dashboard.

How Do You Test a Pepperjam / Ascend Integration Before Going Live? #

Before committing to a wallet design for your pepperjam integration, confirm the following against a real account rather than documentation alone:

• Authenticate against both the ascend by partnerize api and core Partnerize’s API with a single test advertiser, if you have credentials for both, and compare the response shapes directly rather than assuming they match.
• Confirm your two sets of credentials are stored separately in your secrets manager, since they authenticate entirely different systems and a mix-up fails silently rather than loudly.
• Place a test transaction and track how long it takes to appear in reporting on whichever system the advertiser sits on, since neither side has a single well-documented public SLA for this.
• Verify your reconciliation job doesn’t assume every advertiser reports through the same API. Branch the logic explicitly by system.
• Compare tracking software options before you commit engineering time to either system. Our tips for choosing affiliate tracking software covers what to weigh.

Common Pepperjam / Ascend Integration Mistakes #

• Building against only one of the two APIs (Ascend or core Partnerize) and discovering a program you need sits on the other one.
• Directing users or support documentation to the old pepperjamnetwork.com login, which is no longer the standard access point.
• Assuming pre-acquisition Pepperjam payout terms still apply without confirming current terms for your specific account.
• Mixing up the two credential sets in configuration, since both are simple key-based credentials that look similar in a secrets manager.
• Trying to connect Pepperjam to cashback website tracking with only an ascend publisher api key when the target advertiser actually needs a partnerize application key user api key pair.
• Storing the ascend publisher api key and the partnerize application key user api key pair under the same secrets manager entry, making a later rotation error-prone.
• Treating Pepperjam as your only network rather than one piece of a broader integration strategy. Our overview of affiliate network integration covers how to run several networks without them colliding.
• Skipping a comparison against alternatives before settling on Pepperjam specifically. Our review of Trackier alternatives is a useful reference point for evaluating tracking platforms generally.

FAQ

Conclusion #

With Pepperjam, the biggest risk isn’t a bad token refresh or a missed validation window. It’s building against the wrong API entirely because the brand merger left two systems running in parallel. Confirm which platform your target advertisers sit on before you write any integration code, keep the two credential sets clearly separated in configuration, and treat pre-2020 payout terms as historical rather than current. If you’d rather have a team that’s already mapped both systems handle this, talk to our integration team. Our Pepperjam integration services exist for exactly this, and we can save you a rebuild.