Webgains rebuilt its entire publisher API from scratch in recent years, and a webgains integration built against the older documentation will not work against the current system. The Smart Platform API replaced the legacy connection method, moved the publisher dashboard to a new domain, and added real webhook support, a genuine improvement for anyone who previously had to poll for transaction updates.
What Is Webgains Integration? #
A webgains integration connects your publisher account to Webgains‘ European affiliate network, which is part of the ad pepper media group and covers retail, fashion, finance, and travel merchants across the UK, Germany, France, Spain, the US, and beyond. The current publisher dashboard lives at platform.webgains.io, not the older webgains.com login some outdated guides still reference. Webgains appears alongside Awin and TradeDoubler in our roundup of European affiliate networks for cashback businesses, worth reading for direct comparison.
How Does the Webgains Smart Platform API Work? #
The webgains smart platform api, the current generation of the webgains api, is a genuine rewrite (Webgains itself calls it a radical re-write and rationalisation), replacing a legacy API that is now being phased out for most accounts. If you find older integration documentation referencing a different authentication flow, assume it describes the legacy system and confirm against current docs before building.
Authentication #
Modern integrations authenticate using a combination of username, password, client_id, and client_secret, obtained from your Webgains account settings. Full reference is at docs.webgains.dev. A separate API Key is also available specifically for Deals and Program status data, generated by requesting it directly through your account.
What the API Covers #
- Programme synchronization: joined programmes, membership changes, rejected or closed programmes.
- Offers and vouchers: active deals and coupon codes available to promote.
- Transactions, commission, and self-billing invoices and credit notes, accessible programmatically rather than only through the dashboard.
- Webhooks, formerly called Callbacks, for real-time event notification rather than scheduled polling.
How Do Webgains Deep Links Work? #
A webgains deep link is generated per programme through the platform dashboard or via the API’s ads and creative endpoints, following a more conventional query-string structure than TradeDoubler’s format. Because Webgains does not publish a public advertiser directory, the specific brands visible to you depend entirely on which programmes you have already joined, so plan your programme applications before assuming a particular merchant is reachable. If you’re deciding whether to build a custom integration or lean on existing tooling, our overview of affiliate network integration covers that decision generally.
| WORTH KNOWING BEFORE YOU BUILD Webgains’ webhook system (formerly Callbacks) is a meaningful upgrade over polling-only integrations. If your current sync currently runs on a scheduled job, evaluate whether switching to webhook-driven updates would reduce both API load and the lag between a transaction happening and your wallet reflecting it. |
How Does Webgains Data Map to a Cashback Wallet? #
| Webgains concept | Wallet state | What triggers the move |
| Transaction or lead reported | Pending | Sale or qualified lead registers via API or webhook |
| Validation period passes | Confirmed | Advertiser-specific window, no fixed network default |
| Payment frequency threshold met | Withdrawable | Weekly by default, or your selected payout frequency |
| Programme membership rejected or closed | No further transactions expected | Sync job should stop attempting to track a closed programme |
Webgains’ payment frequency is configurable rather than fixed, weekly by default, but you can select a different cycle in the platform. Model that as a per-account setting rather than a hard-coded constant, since it can differ from one Webgains account to another.
What Does Webgains Publisher Approval Require? #
Webgains publisher approval follows the standard pattern: register with the network, then apply to individual advertiser programmes separately.
- Register on the current Smart Platform, not the legacy system, to avoid a migration step later.
- Apply to individual programmes, each advertiser reviews independently.
- Because Webgains does not expose a public directory of every advertiser, expect to discover new programme opportunities primarily through your account contact or the platform’s own recommendations.
- If you already run a Laravel-based platform, our technical note on Laraback affiliate network integration covers the general integration pattern this guide assumes.
Still Polling Webgains Instead of Using Webhooks? #
Our Webgains integration services cover Smart Platform API migration, webhook setup, and deep link generation to build faster and more reliable affiliate tracking workflows.
How Do You Connect Webgains to Cashback Website Reporting? #
The practical path to connect Webgains to cashback website reporting runs through the Smart Platform API for programme sync and transaction data, plus webhooks for real-time updates rather than relying solely on scheduled polling. If your integration currently authenticates against the legacy system, treat a rebuild against the current API as a priority rather than a someday task, since Webgains has already signaled the legacy path is being phased out. For the wider set of networks a European-facing cashback platform typically runs, our roundup of global affiliate networks for cashback websites is a useful map.
How Do You Test This Before Going Live? #
- Confirm your client_id and client_secret authenticate correctly against the current Smart Platform API, not a legacy endpoint.
- Set up a webhook endpoint and verify it receives a test event before relying on it for production transaction updates.
- Generate a deep link for a joined programme and confirm it resolves to the correct destination page, not a generic homepage fallback.
- Pull your self-billing invoice data through the API and reconcile it against what the dashboard shows for the same period.
Common Mistakes to Avoid #
- Building against legacy API documentation instead of the current Smart Platform API, which uses a different authentication flow.
- Relying entirely on scheduled polling when webhook support is available and reduces both load and reporting lag.
- Hard-coding the weekly payment frequency assumption instead of reading it as a per-account configurable setting.
- Continuing to sync a programme after membership has been rejected or the programme has closed.
- Calling old documentation the webgains api without checking whether it actually describes the Smart Platform generation or the deprecated one.
- Assuming the webgains smart platform api and the legacy system share a single set of credentials, they do not.
- Treating webgains publisher approval as a one-time gate rather than something that can vary program by program.
- Not benchmWhere do I log into Webgains today?arking Webgains against other options before defaulting to it. Our comparison of Post Affiliate Pro alternatives covers a related evaluation from a different angle.
FAQ #
Does Webgains have a current API for publishers? #
Yes, the Smart Platform API, a full rewrite of the legacy system, covering programme sync, transactions, commission, offers and vouchers, self-billing data, and webhooks.
Where do I log into Webgains today? #
platform.webgains.io is the current publisher dashboard. Older documentation referencing a different login is describing the legacy system.
Does Webgains support real-time transaction notifications? #
Yes, through webhooks, formerly called Callbacks, which reduce the need for scheduled polling.
How do I connect Webgains to cashback website deep links? #
Generate deep links per joined programme through the dashboard or the API’s ads and creative endpoints, using a conventional query-string format rather than anything unusual.
Who owns Webgains? #
Webgains operates as part of the ad pepper media group, a UK-headquartered European affiliate network.
Conclusion #
A webgains integration built today should target the Smart Platform API specifically, not the legacy system still referenced in older guides. Set up webhooks rather than relying purely on polling, treat payment frequency as a per-account setting, and confirm your program sync correctly stops tracking closed or rejected relationships. If you would rather not build this yourself, talk to our integration team. Our Webgains integration services exist for exactly this, and we can take it from here.
