Recharge Changelog logo
Back to Homepage Subscribe to Updates

Changelog

What's New at Recharge?

Labels

  • All Posts
  • New
  • Enhancement
  • Fix
  • Acquire Customers
  • Retain Customers
  • Grow the Business
  • Improve Operational Efficiency
  • Automate
  • Analytics
  • API
  • Increase AOV
  • Increase LTV

Jump to Month

  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • November 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • August 2020
  • July 2020
  • June 2020
  • April 2020
  • March 2020
  • February 2020
  • December 2019
  • November 2019
  • October 2019
Changelog byAnnounceKit

Create yours, for free!

EnhancementAPI
2 weeks ago

Cursor-based pagination is now required for API calls returning responses with >100 pages

As of May 1, 2025, both versions of the Recharge API (2021-01 & 2021-11) require cursor-based pagination for responses that exceed 100 pages.


Requests that return more than 100 pages must now use cursor-based pagination. Otherwise, the request will result in an error.

Who is impacted?

There is no impact to merchants currently using these endpoints without cursor pagination — they have been added to a whitelist, and can temporarily continue using page-based pagination.

This change applies to merchants who are not currently using page-based pagination to return 100+ pages of data. Any new API requests will require the use of cursor-based pagination.

For more information on cursor-based pagination, see our API documentation.

API
3 months ago

Upcoming Change to Recharge API - 90-day Lookback Limit for Processed Charges

Starting March 19th, 2025, we’re making changes to our retrieve, and list charge endpoints on API versions 2021-01 and 2021-11. Success, refunded, or partially- refunded processed charges over 90 days ago will no longer appear in the results. Please review your integration accordingly. 


In 2025, Recharge is thrilled to improve our speed, scalability, and data analysis capabilities for your store. These enhancements will lead to more robust features and faster API and page load times.

What You Need to Do

Please review your API integration for any impacts and update your API calls, if necessary, that fetch charges with a processed_at date older than 90 days (whether fetching an individual charge or a list of charges).

Please note:

  • GET requests will only return charges processed within the last 90 days. Otherwise, it will result in an empty list.

Charge data processed over 90 days ago will remain available through the Exports tool in your Recharge merchant portal and within the Merchant portal UI.

Examples of unaffected API calls:

  • [LIST CHARGES] /charges?status=queued
  • [LIST CHARGES] /charges?status=error
  • [RETRIEVE A CHARGE] /charges/{id}  (if it's a charge that does not have a processed_at date or the processed_at date is within the last 90 days)

Examples of API calls that may return partial results:

  • [LIST CHARGES] /charges?processed_at_min=2024-01-01 (this would only return results that have a processed_at date in the last 90 days)
  • [LIST CHARGES] /charges?status=success, queued (this would return all queued charges but only return success charges that have a processed_at date in the last 90 days)
  • [LIST CHARGES] /charges?ids={id},{id},{id}  (this would only return charges that do not have a processed_at date or the processed_at date is within the last 90 days)

Examples of API calls that will result in an empty list:

  • [LIST CHARGES] /charges?processed_at_max=2024-01-01 (any date over 90 days old)

Example of API calls that will result in a 404: 

  • [RETRIEVE A CHARGE]/charge/{id} (if it's a charge with a processed_at date older than 90 days)
API
4 months ago

API Update - Blocking API Calls when Recharge App Uninstalled

As of today, January 16th, the Recharge API will return HTTP 403 errors when requests come from an API token associated with stores that no longer have Recharge installed.


If a store reinstalls Recharge, their API token will be functional again.

EnhancementAPI
a year ago

Update to Manual Order Processing

We are implementing changes to the charge date for manually processed orders. Starting May 21st, we will introduce a change to order processing. If an order is manually processed through the merchant portal, customer portal, or the API before its scheduled charge date, we will adjust the charge date to match the processing attempt date.

Here is an example of the before and after:

  • Currently: On May 10th, a customer enters their customer portal and opts to immediately ship an order that was scheduled for June 1st; we would maintain the charge date as June 1st.
  • This change will begin coming into effect for some stores on May 21st: On May 10th, a customer enters their customer portal and opts to immediately ship an order that was scheduled for June 1st; we will update the charge date to May 10th to align with the processing attempt date. (This would happen regardless of whether the payment attempt succeeds or fails)
This change may affect you if you rely on the charge date field to analyze data for orders processed earlier than their originally scheduled date.

Additionally, we are introducing a new field that indicates the original charge date set when the order was created. This field will be denoted as original_charge_date in our API and Exports. For additional information, please refer to our documentation.
EnhancementImprove Operational EfficiencyAPI
a year ago

Access a running log of all store events with the new Events API resource

All merchants on the Pro plan or higher can now use the all-new Events API resource to fetch a read-only running log for all events on a store within the last 7 days. 



Uses of this resource include but are not limited to:

  • Granular analytics
  • Data synchronization
  • Advanced troubleshooting and
  • Recovery if webhook receivers experience short-term failure

How does it work? Review our API reference documentation.

NewAPI
2 years ago

Announcing Javascript SDK for storefront customizations!

All merchants on Pro / Custom pricing plans now have access to two new powerful tools that dramatically accelerate storefront (subscriber-facing) customizations. For more info, read the blog post from our product team here.


Storefront API Access

Leverage the same REST API, but with additional capabilities like: 

  • Secured API access directly within the browser with built-in authentication
  • Automatic filtering of data/functionality based on the needs of the use case
  • Cost savings by eliminating proxy servers and interstitial layers and much more!

Create a Storefront API token today! 

Javascript SDK for Storefront Customizations

Let your code write itself with capabilities like: 

  • Fully typed SDK to enable auto-complete and improved debugging
  • Pre-made functions for common tasks
  • Platform independent SDK that works with Shopify storefront, Hydrogen Apps, React apps, and a host of other technology frameworks.

How does it work? Visit our dedicated SDK documentation here. 

API
2 years ago

Sync canceled subscriptions with current offerings

You will now be able to use the Recharge API, more specifically the “update a subscription” endpoint, to make any changes to a canceled subscription. Moving forward, if your customers choose to reactivate their canceled subscriptions at any point, those subscriptions will continue to align with your current offerings, saving you time from manually making updates. This can be done using the new bulk updater and also works on the bulk update resource and in asynchronous batches. This also now works when bulk managing subscriptions in the Recharge admin UI.

How does it work? Learn more here.

NewAPI
2 years ago

Use Theme Engine API endpoints to skip and unskip multiple subscriptions

When customers choose to skip or unskip, all operations will perform simultaneously, which can increase the speed of operations by 5x. Customers will see a decrease in waiting time once they choose to skip or unskip, and those customers that average more than one subscription or have onetimes will see an improvement.

How does it work? Learn more here.

EnhancementAPI
2 years ago

Improvements to Customer Delivery Schedules API

With this improved endpoint, we've added functionality and information including: 

  • Adding and removing variants on queued prepaid orders now correctly reflect on the delivery schedule
  • Payment methods are now visible on the order within Delivery Schedules
  • Prepaid orders are priced at zero, but we have maintained visibility for the original line item price

How does it work? Learn more here.

NewAPI
2 years ago

Use Theme Engine to create a customized bundling experience

If you are on the Recharge Pro or Enterprise plan you can now read and update bundle-related data with new bundle selection endpoints. 

How does it work? Learn more here.