Start Import Upload — POST /api/v1/project-imports/uploads
Start Import Upload
Open a parted upload (ADMIN): a NEW import job in uploading (201), or — the token checked FIRST — the caller’s existing non-failed job of that client_token (200, with its received parts or its later status). Then the name check: 422 name_invalid / 409 name_taken. Nothing is read.
Endpoint: POST /api/v1/project-imports/uploads
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
- Your role must be Admin or higher.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”| Content type | Body | Required |
|---|---|---|
application/json | ProjectImportUploadStart | yes |
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
201 | Successful Response | ProjectDataJobRead (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.
More details
Section titled “More details”- Group: Project data
- Operation ID:
start_import_upload_api_v1_project_imports_uploads_post - Source code:
backend/app/routers/project_data.py, line 438 - Specification: OpenAPI JSON