Create a category

POST $BASE_URL/v1/categories

Auth: Authorization: Bearer <accessToken> — an organization-scoped token from Authentication. Integrator API users carry the category management permission by default.

Categories are also created automatically when you send items[].categories on transactions — see menu synchronization. Use this endpoint when you want to upload or manage the category tree explicitly.

​

Payload schema

{
  "name": { "TR": "…", "EN": "…" },
  "description": "…",
  "opaqueId": "…",
  "parent": "category-uuid",
  "types": {}
}

​

Body

status is not accepted in the body — records are always created with 1 (use the delete endpoint to remove a category). organization is derived from your token; you cannot create categories for another organization. Fields outside the schema are silently dropped; type errors return 400 with the individual validation messages joined in message.

​

Example

curl --request POST \
  --url "$BASE_URL/v1/categories" \
  --header 'Authorization: Bearer <accessToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "name": { "TR": "Espresso Bazlı", "EN": "Espresso Based" },
    "opaqueId": "espresso-based",
    "parent": "1e1cc0fb-55a1-4679-80df-6dccb936273f"
  }'

​

Response

{
  "id": "79a83256-2925-44b4-9bdc-a401caccf969",
  "name": { "TR": "Espresso Bazlı", "EN": "Espresso Based" },
  "organization": "07f84834-1184-4eb6-82f5-7eda13231fc3",
  "status": 1,
  "opaqueId": "espresso-based",
  "parent": "1e1cc0fb-55a1-4679-80df-6dccb936273f",
  "createdAt": "2026-09-18T09:23:28.303Z",
  "updatedAt": "2026-09-18T09:23:28.303Z"
}

• organization is set server-side from your token — trust the values in the response, not what you sent.
• parent is not validated — sending an unknown id still creates the record; keeping the hierarchy consistent is the caller’s responsibility.
• Optional fields you did not send are omitted from the response — do not expect null.