Upload an archive as the next project revision (multipart)

POST 
/api/v1/projects/:project_id/revisions/upload

Append an uploaded archive to an archive-series project.

Head-SHA short-circuit: bytes identical to the target ref's head return the existing head row — no new row, no object storage PUT (mirror of the assessment upload endpoint). VCS-source projects are rejected (use /sync or POST /revisions); sourceless projects must attach an archive source first.

• Scope required: projects:manage_source + manager-or-above.
• Archived projects reject the append (409).

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.