> 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.md).

# Attribute Config Groups

Administrative endpoints for **attribute config groups** — named, ordered labels that organise product attribute configurations in the management panel.

### Core Capabilities

**1. Listing**

* Retrieve a paginated list of all attribute config groups.
* Results are ordered by `order` (ascending) by default.
* Use the `sort` query parameter to order by any field (`pk`, `name`, `order`).

**2. Full CRUD**

* Create a new attribute config group with a unique name.
* Retrieve, fully update, partially update, or delete an existing group by its identifier.

### Dynamic Settings & Environment Variables

**Dynamic settings:** No dynamic settings affect these endpoints.

**Environment variables:** No environment variables affect these endpoints.


---

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