Features Comparison Compare Freemius to EDD, WooCommerce, and CodeCanyon/ThemeForest.
Software Licensing Control what features to enable based on the plan and number of site activations.
Subscriptions Build a sustainable recurring revenue stream.
Automatic Updates Manage and deploy versions all in one place.
Buy Button Easily embed a buy button on your website.
Analytics & Usage Tracking Get actionable insights on user behavior.
User Dashboard A fully-featured members area for customers.
Affiliate Platform Manage affiliates. Track clicks, visits & referrals.
Cart Abandonment Recovery Recover lost sales with automated emails.
EU VAT & UK VAT Offload VAT handling to Freemius.
US Sales Tax Pass sales tax liability to Freemius.
Selling WordPress Plugins The definitive guide on selling plugins successfully, from ideation to launch (and beyond).
Documentation Start by integrating your WordPress plugin or theme in 5 mins to get all our platform features.
Getting Started Getting Started 🚀Integration & ConfigTesting & DebuggingVersion DeploymentLicensing APIBuy Button JS API
Popular Topics Getting PaidSelling Add-OnsBundles & MembershipsOffering Free TrialsUser's Dashboard
WordPress SDK
PHP SDK
System Status
Changelog
PricingCustomers BlogVideosPodcast MarketingCustomer SupportInterviewsProduct FAQ

Changelog / Optimizing Webhook Payloads: Removal of Developer Data

Optimizing Webhook Payloads: Removal of Developer Data

Freemius provides a webhook mechanism for seamless integration with your software. We recently discovered that some webhook payloads were unintentionally including developer data. To optimize network payloads, we will no longer be sending this data. All other entities and payloads will remain unchanged. For example, the license.created webhook will continue to receive the license object as expected.

This inclusion of developer data was an oversight on our part, and since it was never documented, we have no reason to believe it was actively used. However, if you were relying on it, you have two options:

  1. Retrieve the developer data directly via the API when needed.
  2. Recommended: Store the developer data in an environment variable or cache it within your system. Since this data rarely changes, frequent API calls or webhook-based retrieval are unnecessary.