> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/ai-in-umbraco/19.latest/management-api/contexts/create.md).

# Create Context

Create a new AI context.

Creates a new context for storing brand voice, guidelines, or content resources.

## Request

```http
POST /umbraco/ai/management/api/v1/contexts
```

### Request Body

{% code title="Request" %}

```json
{
    "alias": "brand-voice",
    "name": "Brand Voice",
    "resources": [
        {
            "resourceTypeId": "text",
            "name": "Tone of Voice",
            "description": "Writing style guidelines",
            "sortOrder": 0,
            "settings": "Always use a friendly, professional tone...",
            "injectionMode": "Always"
        }
    ]
}
```

{% endcode %}

### Request Properties

| Property    | Type   | Required | Description             |
| ----------- | ------ | -------- | ----------------------- |
| `alias`     | string | Yes      | Unique alias (URL-safe) |
| `name`      | string | Yes      | Display name            |
| `resources` | array  | No       | Collection of resources |

### Resource Properties

| Property         | Type   | Required | Description                      |
| ---------------- | ------ | -------- | -------------------------------- |
| `resourceTypeId` | string | Yes      | Type of resource                 |
| `name`           | string | Yes      | Display name                     |
| `description`    | string | No       | Optional description             |
| `sortOrder`      | int    | No       | Order for injection (default: 0) |
| `settings`       | object | No       | Resource content                 |
| `injectionMode`  | string | No       | `Always` (default) or `OnDemand` |

## Response

### Success

Returns the newly created context's ID (as a string) with a `Location` header pointing to the Get Context endpoint.

{% code title="201 Created" %}

```json
"3fa85f64-5717-4562-b3fc-2c963f66afa6"
```

{% endcode %}

### Validation Error

{% code title="400 Bad Request" %}

```json
{
    "type": "https://tools.ietf.org/html/rfc7231#section-6.5.1",
    "title": "Duplicate alias",
    "status": 400,
    "detail": "A context with this alias already exists."
}
```

{% endcode %}

## Examples

{% code title="cURL" %}

```bash
curl -X POST "https://your-site.com/umbraco/ai/management/api/v1/contexts" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "alias": "brand-voice",
    "name": "Brand Voice",
    "resources": [
      {
        "resourceTypeId": "text",
        "name": "Tone of Voice",
        "settings": "Always use a friendly, professional tone..."
      }
    ]
  }'
```

{% endcode %}

{% code title="C#" %}

```csharp
var context = new
{
    alias = "brand-voice",
    name = "Brand Voice",
    resources = new[]
    {
        new
        {
            resourceTypeId = "text",
            name = "Tone of Voice",
            settings = "Always use a friendly, professional tone..."
        }
    }
};

var response = await httpClient.PostAsJsonAsync("/umbraco/ai/management/api/v1/contexts", context);
```

{% endcode %}


---

# 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.umbraco.com/ai-in-umbraco/19.latest/management-api/contexts/create.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.