project

Submit Import Job For New Project

Changed on

Start a background import as a NEW project (Door 1, async).

Returns as soon as the project row and the job exist, so the client can navigate straight to a project that reads as not-yet-ready while the import runs. The county is the caller's, picked on the map as on Address Search, so the request path reads no sandbox.

Separate from /sandbox/from-features rather than a branch inside it: that route's upload field means "here are the matches I already resolved", and quietly re-pointing it at background execution would strand a browser tab open across the deploy.

post/api/v1/project/sandbox/from-upload

Request

  • Base URL
    https://api.maia-analytics.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.maia-analytics.com/api/v1/project/sandbox/from-upload
  • Auth
    HTTP bearer

Headers

Idempotency-Keystring nullable

Request body

spine'matched_only' | 'all_rows'
knowledge_skill_workspace_idstring uuid nullable
layer_namestring nullable

Name for the matched-features layer. In-project route only — the new-project route names its layers from the create flow. Blank or absent falls back to a name derived from the matched feature ids.

county_fipsstring required

Response

Successful Response

project_idstring uuid required
import_job_idstring uuid required
county_fipsstring required

Changes