# Create Data Field

Creates a data field with its type, dimensionality and AI description. The field behaves like one created in the app: it appears in the field overview, can be used as a placeholder, filled through the contact endpoints and used in campaigns.

A rejected request creates no field. The response lists one message per problem, naming the attribute and, where applicable, the allowed values or length; a duplicate name names the ID of the existing field.

Endpoint: POST /field/create
Version: 1.0.0

## Request fields (application/json):

  - `name` (string, required)
    Name of the data field; unique within the account, at most 250 characters, no HTML
    Example: Appointment date

  - `type` (string, required)
    Data field type, one of `field-single`, `field-paragraph`, `field-email`, `field-number`, `field-url`, `field-date`, `field-time`, `field-datetime`, `field-html`, `field-decimal` (the types returned by `GET /field/{fieldid}?detail=true`)
    Example: field-datetime

  - `multidimensional` (boolean)
    Whether a contact can hold one value per subscription (true) or one value overall (false)
    Example: true

  - `ai_description` (string)
    Description of the field for AI features and the KlickTipp MCP server; at most 2000 characters, no HTML
    Example: Date and time of a booked appointment. A contact can have several appointments.

## Response 200:

  - `200` (unknown)
    Success Response.

## Response 200 fields (application/json):

  - `id` (string, required)
    ID of the new data field

## Response 403:

  - `403` (unknown)
    Access Denied Response (403).

Your account does not have the required permissions to access this resource.

## Response 406:

  - `406` (unknown)
    Not Acceptable Response (406). The data field was not created.