BusinessStub Keep an existing site on its supported integration
BusinessStub tracks website API, runtime, import, editor, and widget versions separately. A working website should not be upgraded by copying code from another business or changing a version number without review.
For website developers
New integrations use the current authoring template and versioned API paths such as /api/v1/stubs/<slug>/…. Existing registered integrations can use their supported legacy contracts. Production widgets use pinned releases. Ask BusinessStub for the current integration instructions before preparing a new deployment.
Coordinate compatibility updates
When a change requires migration, BusinessStub coordinates the replacement, tests the website, and retains a path to recover from a failed release. Report a compatibility warning with the affected website and feature so the registered deployment can be checked.
Need a hand?
For a setup or access issue, include your business name, the page, and the message you see when contacting BusinessStub. Keep passwords and private customer details out of community posts.
Explore common fixes →