Migration notes
Find the former reference topics and understand changes from the legacy documentation.
The old single-page API and Plugin SDK reference has been reorganized into Markdown guides. The /api and /plugins entry routes translate the former section fragments into their new destinations.
Find an existing topic
| Former topics | New guide |
|---|---|
| Categories, tax, discounts, suppliers, vehicle fitment | Catalog resources |
| Warehouses, inventory, fulfillment, returns, transfers, production, procurement, shipping | Inventory and fulfillment |
| Invoices, credit notes, SevDesk, vendors, affiliates | Finance and partners |
| CSV and image uploads | Data and media |
| CMS pages, subscribers, campaigns, custom emails | Content and email |
| Settings, credentials, jobs, audit, users | Administration |
API changes and corrections
Administrative list pagination now defaults to 50 with a maximum of 500 on endpoints using the shared helper. Individual endpoints can have different response envelopes and limits.
Authentication distinguishes session JWTs, scoped sfk_ tokens, and public pk_sf_ keys. Login with two-factor authentication uses a separate verification step. A token scope is an explicit allowlist, not access to every route in that resource area.
Deployments can split the shared kernel across several API hosts. Use the backend overview to select the correct host. Some legacy registered routes are not exposed by the split backend definitions; the relevant guides identify those cases.
SDKs
The HTTP examples use curl and standard request semantics. The legacy page's client-package and scaffolding claims have not been verified against a published SDK release and are not prerequisites for using the API.
For plugins, start from the working JavaScript package shape. TypeScript consumers should use the plugin SDK version supplied with their kernel environment and check its types against the running implementation.
Plugin distribution and compatibility
The current installer registers packages already resolvable by Node.js. It does not download packages, enforce a coreVersion range, or automatically provision admin pages and HTTP routes from metadata.
Before upgrading a package, check its registration, settings, migrations, and hook usage against the target kernel. Keep applied migration files unchanged and test lifecycle behavior in a development runtime.
Billing and partner programs
Marketplace distribution, plugin billing, certification, and commercial partner terms are separate from the runtime contract documented here. Contact the Sellforge team for the current publishing and commercial process.
Changelog
The historical version labels on the old HTML reference are not a versioned API compatibility guarantee. This documentation records a source-review date and kernel baseline instead. API versioning explains the current URL convention.
Support
For a documentation correction, include the page URL, your kernel version, and the relevant request/response with credentials removed. Email [email protected].
Found something unclear? Let us know