How it works
WhensavePartialSession is enabled, Dromo continuously saves the user’s progress in the background — capturing the active stage, column mappings, transformations, and the uploaded file. Progress is debounced and flushed automatically; no extra code is required.
To enable auto-save:
savePartialSession requires backendSyncMode: "FULL_DATA" and a consistent
importIdentifier to group sessions for the same import type.Security model — the hydrationId
Sessions use a two-token model to prevent a leaked credential from granting permanent access:
When a session is created, both tokens are returned. Pass the
hydrationId to the widget. Store the sessionId server-side so you can mint a fresh hydrationId whenever the user returns.
Starting a session
CallPOST /api/widget/session/v2/auth/ from your backend. The response includes a sessionId to store and a hydrationId to pass to the widget.
import_identifier and a custom token TTL:
Response:
sessionId— persist this server-side. It is needed to resume or delete the session later.hydrationId— pass this to the widget to begin the session.
Restoring a session
When the user returns to resume an import, mint a freshhydrationId from your backend using the stored sessionId, then pass it to the widget.
Step 1 — Re-issue a hydrationId
Response:
Step 2 — Pass to the widget
hydrationId to fetch the saved state and resume from where the user left off.
Deleting a session
Sessions are automatically cleared when an import completes. To delete manually, send aDELETE request with the session’s UUID and your backend license key:
Response:
hydrationId return 403. This call is idempotent and returns success: true even if the session was already deleted.
Error reference
Full endpoint reference
All endpoints requireX-DROMO-LICENSE-KEY (backend license key).
