> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/server-side/command-line-interface/resource-loader/feature-experimentation/project.md).

# Project

Schema, including its fields, nested structure, and relationships

#### Definition

A **Project** is a simple container used to group campaigns. It does not affect campaign execution or hierarchy beyond the organization. Projects can help users categorize campaigns (for example, by department or project).

#### Payload Properties

For project creation or update, the payload is very simple:

* **`id`** (Integer, *optional*) – The project's unique ID. Include this only when updating an existing project.
* **`name`** (String, *required*) – Project display name.

**Example Project Payload:**

```json
{
  "name": "Marketing Campaigns"
}
```

#### Response Fields

When a Project is retrieved, it will include:

* **id** (Integer) – The unique ID of the Project.
* **name** (String) – The project name.

**Example Project Response:**

```json
{
  "id": "project_id",
  "name": "Marketing Campaigns"
}
```

#### Error Codes

Potential errors for Project operations:

* **InvalidPayload** – Missing project name when creating a project, or other payload formatting issues.
* **PermissionDenied** – User not allowed to create projects (if such permission is restricted).

*(Projects don’t involve parent relationships, so errors like ParentNotFound or InvalidDependency are generally not applicable, except as generic error responses. The above codes mirror the general ones.)*


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/server-side/command-line-interface/resource-loader/feature-experimentation/project.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.