Legacy Totalum SDK
Older projects keep working exactly as they do today.
Legacy projects keep working forever. No migration is needed, nothing will be switched off, and every endpoint and SDK method they use keeps its behaviour. You can keep building, publishing and editing them as you always have.
Want one on the new engine? Migrate to the New Engine copies it, with its data and files, into a new project and leaves this one untouched (Starter plan, 50 credits).
A project is a legacy project when it was created before 8 October 2026, or created without the v2 engine. You can tell from Get Project: a current project has engineVersion: "v2"; a legacy project has no engineVersion.
Legacy projects use a different database and SDK from current projects, so their reference lives here:
| Page | What it covers |
|---|---|
| Legacy project database | The built-in database of legacy projects |
| Get all data from your project | Export every record as JSON or Excel |
| Legacy Database SDK | The totalum-api-sdk package: CRUD, filters, files, PDFs, AI, scanning, scraping and e-mail |
| Legacy Database API | The REST endpoints that read and write a legacy project's records |
| Legacy projects: what differs | Which endpoints and features of the current API legacy projects do not have |
Everything else in these docs — the App Builder API, the Totalum SDK, the MCP server — describes the current engine. New projects are created on it automatically.