Upcoming shutdown of legacy multiparser and bumper endpoints

Scheduled for Oct 15, 10:00 - 12:00 EDT

Scheduled

As part of ongoing improvements to our SDK infrastructure and deployment model, we're retiring a set of endpoints that will no longer be reachable after December 14, 2026. After that date, these endpoints will be permanently decommissioned, and any calls to them will start failing.

We'd encourage you to check whether your integration depends on any of these calls, so their removal doesn't cause unexpected issues. The Content Services API and the editor instance methods already cover the same needs and are fully documented.

Endpoints being retired:

Multiparser
https://bee-multiparser.getbee.io
https://delayed-bee-multiparser.getbee.io
Paths starting with /api/v3/parser/ (/email, /page, /popup)

Bumper
https://bee-bumper.getbee.io
https://delayed-bee-bumper.getbee.io
Paths including /message and /bump-row

To help you confirm the impact ahead of time, we’ll run two brownout windows in the weeks leading up to the shutdown, temporarily disabling these endpoints so you can verify whether your integration depends on them, rather than finding out on the shutdown date itself:

October 15, 2026, at 7:00 AM PDT / 10:00 AM EDT / 4:00 PM CEST: a short 2-hour brownout, for an initial check.
November 3, 2026 (exact time will be shared closer to the date): a longer brownout lasting approximately 8 hours, for more thorough validation.

If you have any questions, feel free to reach out to our Support Team at sdksupport@beefree.io.
Posted Oct 14, 2026 - 08:51 EDT
This scheduled maintenance affects: API.