Create a project

POST 
/api/v1/projects

Create a customer project (PROJ-ORG-CODE public id).

• Scope required: projects:create + manager-or-above role.
• Gated by the admission-only release_projects flag (404 when off).
• Enforces Organization.max_projects (400 when at the limit).

Everything the body carries is resolved BEFORE the insert — the cap, then the source's connection lineage, then the assignment ids — so every refusal leaves zero rows behind and the project is written once. That ordering is what removes the compensating delete the two-call create needed, along with its own failure arm.

The body is permissive: a project with no source and no targets is legal. What a project can run is decided at assessment start, where those preconditions already live.

Request

Responses

200

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.