> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/admin/products/attribute-config-groups/create-an-attribute-config-group.md).

# Create an attribute config group

Creates a new attribute config group. The `name` must be unique across all groups.

```json
{"openapi":"3.1.0","info":{"title":"Admin API","version":"1.0.0"},"tags":[{"name":"Attribute Config Groups","description":"Administrative endpoints for **attribute config groups** — named, ordered labels that organise product attribute configurations in the management panel.\n\n## Core Capabilities\n\n**1. Listing**\n* Retrieve a paginated list of all attribute config groups.\n* Results are ordered by `order` (ascending) by default.\n* Use the `sort` query parameter to order by any field (`pk`, `name`, `order`).\n\n**2. Full CRUD**\n* Create a new attribute config group with a unique name.\n* Retrieve, fully update, partially update, or delete an existing group by its identifier.\n\n## Dynamic Settings & Environment Variables\n\n**Dynamic settings:** No dynamic settings affect these endpoints.\n\n**Environment variables:** No environment variables affect these endpoints."}],"servers":[{"description":"Omnitron Remote Proxy (external access — recommended)","url":"https://{omnitron_url}/api/v1/remote/{channel_id}","variables":{"omnitron_url":{"default":"sandbox.akinon.com","description":"Omnitron server URL (e.g., {omnitron.akinon.com})"},"channel_id":{"default":"1","description":"The channel identifier the remote request is routed through"}}},{"description":"Commerce API Server (internal / direct access only)","url":"https://{commerce_url}/api/v1","variables":{"commerce_url":{"default":"sandbox.akinon.com","description":"Internal commerce server URL, reachable only from within the Omnitron network"}}}],"security":[{"tokenAuth":[]}],"components":{"securitySchemes":{"tokenAuth":{"type":"apiKey","in":"header","name":"Authorization","description":"Token credential sent in the Authorization header, in the form: `Token <your-token>`. Requires a staff (admin) account."}},"schemas":{"AttributeConfigGroupRequest":{"type":"object","description":"Fields for creating or fully replacing an attribute config group.","required":["name"],"properties":{"name":{"type":"string","maxLength":255,"description":"Unique display name of the group. Must be unique across all attribute config groups."},"order":{"type":"integer","minimum":0,"description":"Sort order. Lower values appear first. Defaults to `0` when omitted.","default":0}}},"AttributeConfigGroup":{"type":"object","description":"An attribute config group record.","properties":{"pk":{"type":"integer","readOnly":true,"description":"Unique identifier of the attribute config group."},"name":{"type":"string","maxLength":255,"description":"Unique display name of the group."},"order":{"type":"integer","minimum":0,"description":"Sort order used when listing groups. Lower values appear first.","default":0}},"required":["pk","name","order"]},"ValidationError":{"type":"object","description":"Returned when the request contains invalid or missing data. Errors are grouped by the field they apply to: each key is the name of a field from the request and its value is a list of one or more messages describing what is wrong with that field. Messages that do not belong to any single field are grouped under `non_field_errors`.","properties":{"non_field_errors":{"type":"array","description":"Error messages that apply to the request as a whole rather than to a specific field.","items":{"type":"string"}}},"additionalProperties":{"type":"array","description":"The list of error messages for the field named by the key.","items":{"type":"string"}}},"Error":{"type":"object","description":"An error response.","properties":{"detail":{"type":"string","description":"A human-readable description of the error."}},"additionalProperties":true}},"responses":{"ValidationError":{"description":"The request contains invalid or missing data.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ValidationError"}}}},"Unauthorized":{"description":"Authentication credentials were not provided or are invalid.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"Forbidden":{"description":"The authenticated user does not have administrator privileges.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}}},"paths":{"/attribute_config_group/":{"post":{"tags":["Attribute Config Groups"],"operationId":"createAttributeConfigGroup","summary":"Create an attribute config group","description":"Creates a new attribute config group. The `name` must be unique across all groups.","requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/AttributeConfigGroupRequest"}}}},"responses":{"201":{"description":"The attribute config group was created.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/AttributeConfigGroup"}}}},"400":{"$ref":"#/components/responses/ValidationError"},"401":{"$ref":"#/components/responses/Unauthorized"},"403":{"$ref":"#/components/responses/Forbidden"}}}}}}
```


---

# 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://apidocs.akinon.com/commerce-openapis/admin/products/attribute-config-groups/create-an-attribute-config-group.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.
