Stage a migration item from uploaded files
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Migration ID
Request Body required
Section titled “Request Body required ”object
Source documents for one item (one detected application group) in this migration.
Optional display name for the item. Defaults to the first file name.
Responses
Section titled “ Responses ”object
Migration item ID
Example
507f1f77bcf86cd799439011Owning migration ID
Example
507f1f77bcf86cd799439011Application created from this item once the run processes it
Example
507f1f77bcf86cd799439011Display name for the item: the created application’s current name when it has one (mirrors the application page, DEV-2729), else the operator-typed item label
Applicant entity type (BUSINESS/INDIVIDUAL); null defaults to business
Pipeline checkpoint. IN_PROGRESS + APP_READY means seeded but still waiting behind the queue (shown as Queued in the UI)
Staged source files
object
Original uploaded file name
Uploaded file MIME type
Uploaded file size in bytes
Number of staged source files
Per-file pipeline progress counts
object
Files whose content classification has finished
Files summarized during the extraction stage
Per-document validations completed (can exceed fileCount — one file fans out to several document types)
File currently being processed in the active pipeline stage
Onboarding completion percent (0-100) during the finalize stage
Total documents queued for the validate stage — the denominator for “validated / N documents” (null before validate)
Post-run gap summary
object
Labels of required profile fields still unfilled once document extraction settled
Truncated error message when the item failed
When this item started processing
Example
2026-03-30T12:00:00.000ZWhen this item finished processing
Example
2026-03-30T12:01:00.000ZDate the item was created
Example
2026-03-30T10:00:00.000ZDate the item was last updated
Example
2026-03-30T12:01:00.000ZWhether an operator may re-run this item: a settled status (MISSING_DATA / FAILED / CANCELLED) whose application (if any) is still PENDING. False once the app has SUBMITTED/APPROVED — re-running would re-extract and overwrite reviewed data.
Example
{ "id": "507f1f77bcf86cd799439011", "migrationId": "507f1f77bcf86cd799439011", "applicationId": "507f1f77bcf86cd799439011", "name": "string", "entityType": "BUSINESS", "status": "QUEUED", "stage": "PENDING", "files": [ { "fileName": "string", "mimeType": "string", "size": 0 } ], "fileCount": 0, "progress": { "classified": 0, "summarized": 0, "validated": 0 }, "activeFile": "string", "onboardingPercent": 0, "validateTotal": 0, "outstanding": { "missingFields": [] }, "error": "string", "startedAt": "2026-03-30T12:00:00.000Z", "completedAt": "2026-03-30T12:01:00.000Z", "createdAt": "2026-03-30T10:00:00.000Z", "updatedAt": "2026-03-30T12:01:00.000Z", "retryable": false}