Shutdown of legacy multiparser and bumper endpoints

Scheduled for Dec 14, 00:00 EST  -  Dec 15, 00:00 EST

Scheduled

As part of ongoing improvements to our SDK infrastructure and deployment model, we're retiring a set of endpoints.
As of today, December 14, 2026, the endpoints listed below are permanently decommissioned, and any calls to them will start failing.

If you are experiencing any issues, we encourage you to check whether your integration depends on any of these calls. The Content Services API and the editor instance methods already cover the same needs and are fully documented here: https://docs.beefree.io/beefree-sdk/apis/content-services-api

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

If you have any questions, feel free to reach out to our Support Team at sdksupport@beefree.io.
Posted Nov 16, 2026 - 06:52 EST
This scheduled maintenance affects: API.