> ## Documentation Index
> Fetch the complete documentation index at: https://docs.contazen.ro/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Expense Category

> Create a new custom expense category for your firm

## Overview

The Create Expense Category endpoint allows you to create new custom expense categories for your firm. You can create both root-level categories and subcategories under existing parent categories.

**Note**: You can only create custom categories - system default categories are pre-defined and cannot be created via the API.

## Request Body

<ParamField body="name" type="string" required>
  The name of the expense category (must be unique within your firm)
</ParamField>

<ParamField body="parent_id" type="integer" default="0">
  Parent category ID. Use `0` for root-level categories, or specify an existing category ID to create a subcategory.
</ParamField>

<ParamField body="is_visible" type="boolean" default="true">
  Whether the category should be visible and available for use when creating expenses.
</ParamField>

## Hierarchy Rules

* **Maximum Depth**: Categories can only be 2 levels deep (category → subcategory)
* **Parent Validation**: Parent categories must exist and belong to your firm
* **Subcategory Limitation**: You cannot create subcategories under existing subcategories
* **Circular Reference**: A category cannot be its own parent

## Response

<ResponseField name="category" type="object">
  The created expense category object

  <Expandable title="Category Object Properties">
    <ResponseField name="id" type="integer">
      Unique identifier for the new category
    </ResponseField>

    <ResponseField name="name" type="string">
      Category name
    </ResponseField>

    <ResponseField name="parent_id" type="integer">
      Parent category ID (0 for root categories)
    </ResponseField>

    <ResponseField name="is_default" type="boolean">
      Always `false` for custom categories
    </ResponseField>

    <ResponseField name="is_visible" type="boolean">
      Whether the category is visible and active for use
    </ResponseField>

    <ResponseField name="type" type="string">
      Always `"custom"` for user-created categories
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="message" type="string">
  Success message confirming the category creation
</ResponseField>

## Validation Rules

* **Name**: Required, must be non-empty after trimming
* **Parent Category**: Must exist and belong to your firm (if specified)
* **Hierarchy**: Cannot create subcategories under existing subcategories
* **Permissions**: Requires write permissions for your firm

<RequestExample>
  ```bash Create Root Category theme={null}
  curl -X POST "https://api.contazen.ro/v1/expense-categories" \
    -H "Authorization: Bearer YOUR_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{
      "name": "Marketing Expenses",
      "parent_id": 0,
      "is_visible": true
    }'
  ```

  ```bash Create Subcategory theme={null}
  curl -X POST "https://api.contazen.ro/v1/expense-categories" \
    -H "Authorization: Bearer YOUR_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{
      "name": "Digital Advertising",
      "parent_id": 5,
      "is_visible": true
    }'
  ```

  ```javascript Create Root Category theme={null}
  const categoryData = {
    name: "Marketing Expenses",
    parent_id: 0,
    is_visible: true
  };

  const response = await fetch('https://api.contazen.ro/v1/expense-categories', {
    method: 'POST',
    headers: {
      'Authorization': 'Bearer YOUR_API_KEY',
      'Content-Type': 'application/json'
    },
    body: JSON.stringify(categoryData)
  });

  const data = await response.json();
  console.log('Created category:', data.category);
  ```

  ```javascript Create Subcategory theme={null}
  const subcategoryData = {
    name: "Digital Advertising",
    parent_id: 5,  // ID of existing parent category
    is_visible: true
  };

  const response = await fetch('https://api.contazen.ro/v1/expense-categories', {
    method: 'POST',
    headers: {
      'Authorization': 'Bearer YOUR_API_KEY',
      'Content-Type': 'application/json'
    },
    body: JSON.stringify(subcategoryData)
  });

  const data = await response.json();
  console.log('Created subcategory:', data.category);
  ```

  ```php Create Root Category theme={null}
  $categoryData = [
      'name' => 'Marketing Expenses',
      'parent_id' => 0,
      'is_visible' => true
  ];

  $curl = curl_init();

  curl_setopt_array($curl, [
      CURLOPT_URL => 'https://api.contazen.ro/v1/expense-categories',
      CURLOPT_RETURNTRANSFER => true,
      CURLOPT_POST => true,
      CURLOPT_POSTFIELDS => json_encode($categoryData),
      CURLOPT_HTTPHEADER => [
          'Authorization: Bearer YOUR_API_KEY',
          'Content-Type: application/json'
      ]
  ]);

  $response = curl_exec($curl);
  $data = json_decode($response, true);
  curl_close($curl);

  echo 'Created category ID: ' . $data['category']['id'];
  ```

  ```php Create Subcategory theme={null}
  $subcategoryData = [
      'name' => 'Digital Advertising',
      'parent_id' => 5, // ID of existing parent category
      'is_visible' => true
  ];

  $curl = curl_init();

  curl_setopt_array($curl, [
      CURLOPT_URL => 'https://api.contazen.ro/v1/expense-categories',
      CURLOPT_RETURNTRANSFER => true,
      CURLOPT_POST => true,
      CURLOPT_POSTFIELDS => json_encode($subcategoryData),
      CURLOPT_HTTPHEADER => [
          'Authorization: Bearer YOUR_API_KEY',
          'Content-Type: application/json'
      ]
  ]);

  $response = curl_exec($curl);
  $data = json_decode($response, true);
  curl_close($curl);

  echo 'Created subcategory: ' . $data['category']['name'];
  ```
</RequestExample>

<ResponseExample>
  ```json 201 - Success theme={null}
  {
    "success": true,
    "category": {
      "id": 25,
      "name": "Marketing Expenses",
      "parent_id": 0,
      "is_default": false,
      "is_visible": true,
      "type": "custom"
    },
    "message": "Category created successfully"
  }
  ```

  ```json 400 - Validation Error theme={null}
  {
    "success": false,
    "error": {
      "message": "Name is required",
      "type": "invalid_request_error",
      "code": "parameter_missing",
      "param": "name"
    }
  }
  ```

  ```json 400 - Invalid Parent theme={null}
  {
    "success": false,
    "error": {
      "message": "Parent category not found",
      "type": "invalid_request_error",
      "code": "invalid_parent",
      "param": "parent_id"
    }
  }
  ```

  ```json 400 - Invalid Hierarchy theme={null}
  {
    "success": false,
    "error": {
      "message": "Cannot create subcategory under another subcategory",
      "type": "invalid_request_error",
      "code": "invalid_parent_level",
      "param": "parent_id"
    }
  }
  ```

  ```json 403 - Permission Denied theme={null}
  {
    "success": false,
    "error": {
      "message": "You don't have permission to create categories",
      "type": "invalid_request_error",
      "code": "permission_denied"
    }
  }
  ```
</ResponseExample>


## OpenAPI

````yaml POST /expense-categories
openapi: 3.1.0
info:
  title: Contazen API
  version: 1.2.0
  description: >
    Build powerful integrations with the Contazen invoicing platform. The
    Contazen API is organized around REST, 

    has predictable resource-oriented URLs, accepts JSON request bodies, returns
    JSON-encoded responses, 

    and uses standard HTTP response codes, authentication, and verbs.


    ## Authentication

    The API uses Bearer token authentication. Include your API key in the
    Authorization header.


    ### Getting your API Key

    1. Log in to your Contazen account

    2. Navigate to Settings > API

    3. Generate or copy your API key (starts with `sk_live_` for production or
    `sk_test_` for testing)


    ### Using the API Key

    Include your API key in the Authorization header:

    ```

    Authorization: Bearer sk_live_YOUR_API_KEY

    ```


    ### Example Request with cURL

    ```bash

    curl --request GET \
      --url https://api.contazen.ro/v1/clients \
      --header 'Authorization: Bearer sk_live_YOUR_API_KEY' \
      --header 'Accept: application/json'
    ```


    ## Rate Limiting

    - 1000 requests per hour per API key

    - 100 create operations per minute per API key


    Rate limit information is included in response headers:

    - `X-RateLimit-Limit`: Maximum requests allowed

    - `X-RateLimit-Remaining`: Requests remaining

    - `X-RateLimit-Reset`: Reset time (Unix timestamp)


    ## Pagination

    All list endpoints return paginated results with the following format:

    ```json

    {
      "success": true,
      "data": {
        "object": "list",
        "data": [...],
        "has_more": true,
        "total": 245,
        "page": 1,
        "per_page": 50,
        "total_pages": 5
      },
      "meta": {
        "version": "v1",
        "request_id": "req_1a2b3c4d",
        "response_time": "23.45ms"
      }
    }

    ```


    ## Multi-Work-Point Access

    API keys belong to a specific work point but can access data from all work
    points

    within the same parent company.


    ## Error Handling

    The API uses conventional HTTP response codes to indicate success or
    failure. 

    In general: 2xx codes indicate success, 4xx codes indicate an error due to
    the 

    information provided, and 5xx codes indicate an error with Contazen's
    servers.


    ## Expanding Nested Objects

    Many endpoints support the `expand` parameter to include related objects in
    the response.

    This follows the Stripe API pattern. For example:

    - `expand[]=lines` - Include invoice line items

    - `expand[]=payments` - Include payment records

    - `expand[]=client` - Include full client object


    ## Localization

    The API supports multiple languages through:

    - `locale` query parameter (en, ro)

    - `Accept-Language` header

    - Default: English
  contact:
    name: Contazen Support
    email: support@contazen.ro
    url: https://contazen.ro
  license:
    name: Proprietary
    url: https://www.contazen.ro/termeni-si-conditii-de-utilizare/
servers:
  - url: https://api.contazen.ro/v1
    description: Production API server
security:
  - bearerAuth: []
tags:
  - name: Authentication
    description: API authentication and test endpoints
  - name: Clients
    description: Manage your customers (B2B and B2C)
  - name: Invoices
    description: Create and manage invoices, proformas, and receipts
  - name: Products
    description: Manage your product and service catalog
  - name: Expenses
    description: Track and manage business expenses
  - name: Expense Categories
    description: Organize expenses with categories
  - name: Suppliers
    description: Manage expense suppliers and vendors
  - name: Settings
    description: API settings and configuration
  - name: Payments
    description: Payments received against invoices
  - name: Receipts
    description: Cash receipts (chitanțe) — standalone or paired with an invoice
  - name: Company Lookup
    description: Romanian company lookup (ANAF / VIES)
  - name: Invoice Series
    description: Manage invoice numbering series
  - name: Bank Accounts
    description: Manage IBAN bank accounts
  - name: E-Factura
    description: Romanian e-invoicing status and configuration
  - name: Supplier Bills
    description: Supplier invoices imported from the ANAF SPV inbox
  - name: VAT Rates
    description: Firm-scoped custom VAT rates on top of the Romanian catalog
  - name: Currencies
    description: Currencies enabled for the firm's bill templates
  - name: Languages
    description: Languages enabled for the firm's bill templates
  - name: Conta
    description: |
      Public ANAF data for the firm's CUI: fiscal profile (TVA scope, RTVAI,
      split TVA, status, e-Factura registration, CAEN) and annual balance
      sheets (cifra de afaceri, profit, capitaluri, datorii, salariați).

      Powered by the public ANAF webservices (no OAuth required for these
      endpoints). The data is cached locally and refreshed on demand via
      the `/sync` actions.
paths:
  /expense-categories:
    post:
      tags:
        - Expense Categories
      summary: Create expense category
      description: Create a custom expense category
      operationId: createExpenseCategory
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ExpenseCategoryCreateRequest'
      responses:
        '201':
          description: Category created
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  data:
                    $ref: '#/components/schemas/ExpenseCategory'
                  meta:
                    $ref: '#/components/schemas/ResponseMeta'
        '400':
          $ref: '#/components/responses/ValidationError'
        '401':
          $ref: '#/components/responses/UnauthorizedError'
components:
  schemas:
    ExpenseCategoryCreateRequest:
      type: object
      required:
        - name
      properties:
        name:
          type: string
          minLength: 1
          maxLength: 100
        parent_id:
          type: integer
          default: 0
          description: Parent category ID (0 for root)
        is_visible:
          type: integer
          enum:
            - 0
            - 1
          default: 1
    ExpenseCategory:
      type: object
      required:
        - id
        - name
        - type
      properties:
        id:
          type: integer
        name:
          type: string
        parent_id:
          type: integer
          nullable: true
        is_default:
          type: boolean
          description: Whether this is a system default category
        is_visible:
          type: boolean
        type:
          type: string
          enum:
            - system
            - custom
        expense_count:
          type: integer
          description: Number of expenses in this category
        children:
          type: array
          items:
            $ref: '#/components/schemas/ExpenseCategory'
    ResponseMeta:
      type: object
      properties:
        version:
          type: string
          default: v1
        request_id:
          type: string
          format: uuid
          description: Unique request identifier for debugging
        response_time:
          type: string
          example: 23.45ms
    ErrorResponse:
      type: object
      required:
        - success
        - error
      properties:
        success:
          type: boolean
          default: false
        error:
          type: object
          required:
            - message
            - type
            - code
          properties:
            message:
              type: string
              description: Human-readable error message
            type:
              type: string
              enum:
                - api_error
                - authentication_error
                - invalid_request_error
                - rate_limit_error
                - permission_error
                - validation_error
            code:
              type: string
              description: Machine-readable error code
            param:
              type: string
              description: The parameter that caused the error
            doc_url:
              type: string
              format: uri
              description: URL to relevant documentation
        meta:
          $ref: '#/components/schemas/ResponseMeta'
  responses:
    ValidationError:
      description: Request validation failed
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    UnauthorizedError:
      description: API key is missing or invalid
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: Use your API key (sk_live_xxx or sk_test_xxx)

````