> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/api-reference/projects-and-submissions.md).

# Projects & submissions

AI Project Builder, durable project lifecycle and community contribution endpoints.

A project is the central collaborative production object in SONIC.

## Routes

```
GET  /api/v1/projects
GET  /api/v1/projects/:id
POST /api/v1/projects/ai-blueprint
POST /api/v1/projects
POST /api/v1/projects/:id/status

POST /api/v1/submissions
GET  /api/v1/projects/:id/submissions
GET  /api/v1/submissions/:id
POST /api/v1/submissions/:id/review
```

## AI Project Builder

`POST /projects/ai-blueprint` accepts an authenticated creator brief and uses a server-side AI provider to create a structured blueprint with title, genre, mood, visual style, scenes, creative tasks and estimated production days.

AI output is a proposal, not an already-created project. The creator explicitly persists it through project creation.

```
CREATIVE PROMPT → AI BLUEPRINT → OPEN PROJECT → CONTRIBUTORS → SUBMISSIONS → REVIEW → REWARDS
```

## Project ownership

`POST /projects` derives owner/account identity from the authenticated session. It does not accept an arbitrary request-body wallet as authorization.

Lifecycle:

```
DRAFT → OPEN → IN_PRODUCTION → REVIEW → COMPLETED → ARCHIVED
```

Status changes must follow the shared transition map. Unauthorized arbitrary jumps are rejected.

## Listing filters

Project listing supports bounded pagination/filtering such as status, creator, type, limit and cursor where implemented by the released source.

## Submissions

Supported submission types include `music_video`, `artwork`, `animation`, `remix`, `short_video`, `trailer`, `story`, `cover_art`, `audio`, and `other`.

Submission lifecycle:

```
DRAFT → SUBMITTED → UNDER_REVIEW
                        ├─ ACCEPTED
                        ├─ REJECTED
                        └─ REVISION_REQUESTED
```

Submitted asset URLs must be public HTTPS resources. Loopback/private targets are rejected.

## Mutation safety

Project creation, submission creation and protected review/status changes use authentication/authorization, validation, rate limiting, tenant-scoped idempotency where applicable, and audit events.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sonic-ai-works.gitbook.io/sonic-networks-docs/api-reference/projects-and-submissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.