generate or update run, mapped to your templates
sheet-by-sheet. This is exactly what the agent proposes to import; show it to your
customer, then refine or execute.
A migration has a preview once a generate/update run reaches
awaiting_approval. Before that, this returns 404.
Authentication
Requires anx-api-key header. See Authentication.
Response
200 OK
string
Always
awaiting_approval when a preview exists.object[]
The templates this migration targets, each
{ slug, name }.object[]
One entry per output sheet:
Choosing columns
Two optional parameters shape which columns come back. Both default off, so leaving them out returns exactly what it always has.string
Comma-separated column names to return, in the order you give them. Matched
exactly and case-sensitive. An unrecognised name returns
400
(unknown_field) listing the valid ones rather than being ignored — a typo
should not quietly leave data out.boolean
default:"false"
Drop columns that hold no data. A column is dropped only when it’s empty in
every row, so the rows you get back all keep the same shape. Empty means
an empty string,
null, or an absent value; whitespace counts as data.
Combine with fields and the pruning applies within your selection.Here “empty” is judged from the rows in this response, which are the whole
payload — a preview is a sample of what the plan would produce, so a column
that’s empty in the sample may still be filled by the real import.
Errors
Example
Next
- Start a run —
updateto refine, orexecuteto import. - Export CSV — get the validated rows after execute.