Get the session log
The settled record of a migration: what was planned, which files went in, who approved what, how many rows were written, and whether existing rows were replaced.
Intended to be fetched once and stored, so you can explain a migration
to your own customer later. It does not include the conversation
transcript — that is /thread — and it does not include individual row
values.
Available once nothing is in flight, including for migrations that
failed: a run can write rows and then fail, which is exactly when this
matters. While a run is active the endpoint returns 409.
Pass ?format=md for the same record as a readable Markdown report.
A migration can be imported again later, so the log always covers every
run to date — a re-fetch is a superset of an earlier one. Use
generated_at to tell snapshots apart.
Authorizations
Your Vern API key. Create one at Settings → API keys.
Path Parameters
The migration ID returned by Create a migration.
Query Parameters
json, md, markdown Response
The session log.
awaiting_files— no files uploaded and no source connectionready— inputs present, no plan yetawaiting_approval— a preview is waiting to be executedcompleted— an import has run successfully
awaiting_files, ready, awaiting_approval, completed