Upcoming Changes
📢 MediaStore API: Password Reset Will No Longer Return 404 for Unregistered Email Addresses
Starting with the release on 23 November 2026, the Reset password endpoint (PUT /customers/passwords) will return the same successful response 200 for every valid password reset request, whether or not a customer account exists for the email. This change aligns with security best practices for prevention of unauthorized account lookups.
What you need to know
- The reset email is sent only when an account exists for the email.
- The endpoint will no longer return
404with error codeUSER0004.
What you need to do
- If your integration handles the
404/USER0004error, you may need to review any related UI messaging before the release on 23 November 2026. Nothing will stop working either way. - On the screen shown after a reset request, we recommend wording such as: "If an account exists for this email, you'll receive a link to reset your password."
- If your code doesn't handle
404/USER0004from this endpoint, no change is needed.
📢 Upcoming Code Freeze
To ensure platform stability through the holidays, we will soon enter our normal end-of-year code freeze.
Below are the details and key information regarding this period.
Code Freeze Period
- Start Date: 16 December 2026
- End Date: 12 January 2027
What you can expect
- No new features or significant changes will be introduced to the codebase, unless they are critical fixes.
- Ongoing projects or feature updates will resume after the code freeze period.
- We will continue to monitor systems to ensure smooth operations.
We kindly ask you to adjust your plans accordingly, and we truly appreciate your understanding and cooperation.
New
✨ Zapier: Cleeng App Now Available
Cleeng is now listed on Zapier, so you can use Cleeng subscriber events to trigger automated workflows in the apps your team already uses.
Learn more
Find out more on the Cleeng app page on Zapier.
✨ Cleeng MCP Server: Now Listed in Claude's Connectors Directory
You can now connect the Cleeng MCP Server directly from Claude's Connectors Directory, without setting it up as a custom connector.
Learn more
Find out more on the Cleeng page in Claude's Connectors Directory.
✨ Hosted Customer Flows: Hungarian Language Added
We have added support for Hungarian in Hosted Customer Flows.
Learn more
Find out more about Hosted Customer Flows and the supported languages.
Improvements
🚀 Hosted Customer Flows: Payment Method Removal Restricted in My Account
Your customers can no longer remove a payment method in My Account while it pays for a subscription that is active or pending cancellation (canceled but not yet ended): the payment method edit view no longer shows the option to remove it. They can remove it after that subscription ends.
What you need to know
Customers can still replace the payment method under Current payment method > Edit with a new card or another available payment method.
What you need to do
No action is required on your side. The update is automatic.
Learn more
🚀 Cleeng Dashboard: Free Trial Setting Moved to Advanced Options
When you set up a subscription offer in the Cleeng Dashboard, the Free trial setting is now in the Advanced options of the Pricing step.
What you need to do
No action is required. Only the location of the setting has changed.
Where to find it
Go to Cleeng Dashboard > Offers & Coupons > Offers, select Subscription, and then go to the Pricing step. Select +Advanced options to see the Free trial setting.
Learn more
API Changes
Updated
🚀 Core (3.1) API: Mark an externally-managed subscription as a trial after it’s created with the Update subscription endpoint (PATCH /3.1/subscriptions/{subscriptionId})
What’s new
Until now, an externally-managed subscription could be marked as a free trial only when it was created. Afterwards, the trial could be ended but not started. You can now also start the trial later, by sending inTrial: true.
Why it matters
Some platforms report the trial separately from, and after, the purchase. Before this change, those subscriptions stayed recorded as regular subscriptions. Now they can be correctly marked as trials, and each trial start and end is recorded in the subscription’s history.
What you need to do
If you only use inTrial: false to end trials, no action is needed.
If your integration sends inTrial: true, check it. Until this release the endpoint ended the trial for any inTrial value, including true. From this release inTrial: true starts a trial and is rejected if a subscription is already in trial. If your integration sends true to end a trial, change it to false.
inTrial must be a boolean. Any other value, for example the string "true" or the number 1, now returns a 400 error.
->>><<<-
Click here to subscribe to our release notes emails and we will send them over to your inbox.