> ## Documentation Index > Fetch the complete documentation index at: https://cactal.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Create an item > Creates an item at the end of the collection’s manual order. Scalar values go in `data` keyed by field key and are validated against the field types — unknown keys are rejected, required fields must be present, `plain_text` and `markdown` are capped at 1,048,576 bytes (markdown must not contain raw HTML), `date` values are ISO 8601 with timezone, and `color` values are normalized to hex. Relationship and asset values go in the side maps: `references` (`reference`: an item id; `multi_reference`: an ordered array of up to 1,000 ids), `images` (`image`: an asset id or `{ assetId, altText }`; `gallery`: an ordered array of up to 25 of those), and `files` (`file`: an asset id or `{ assetId }`). `slug` is optional — it is derived from `data.title` or `data.name` when omitted. Set a non-future `publishedAt` to create an already-published item, or a future `publishAt` to schedule it; the two fields are mutually exclusive. ## OpenAPI ````yaml /api-reference/openapi.json post /cms/collections/{collectionId}/items openapi: 3.1.0 info: title: Cactal API version: 1.0.0 description: >- The Cactal public API. Create, edit, publish, and operate websites programmatically. Authenticate every request with an API key sent as `Authorization: Bearer `. servers: - url: https://api.cactal.ai/v1 security: - apiKey: [] tags: - name: Documentation description: >- Search and read the Cactal product documentation for concepts, guides, agent workflows, platform behavior, and API operations. - name: Feedback description: >- Submit free-form product feedback from users and agents to the Cactal feedback inbox. - name: Websites description: >- Create and manage websites — the top-level resource that owns source code, content, assets, domains, and analytics. - name: Website editors description: >- Grant, list, and revoke website-scoped editor access, and invite collaborators to a single website by email. - name: API keys description: >- Create, scope, rotate, and revoke the API keys that authenticate programmatic and agent access. - name: Source code description: >- Read and edit the framework source files of a website draft. Mutations require an edit lease. - name: Publishing description: Validate, build, publish, and roll back website versions. - name: CMS collections description: >- Define the content model: collections of structured content owned by a website. - name: CMS fields description: Manage the typed fields that make up a collection schema. - name: CMS items description: >- Create, query, publish, and organize the content entries inside a collection. - name: Domains description: >- Manage platform subdomains and custom domains, including DNS verification and the primary domain. - name: Assets description: Upload and manage website files and images served from the Cactal CDN. - name: Media generation description: >- Generate reference-guided website images that are stored as ordinary Cactal CDN assets. - name: Project Context description: >- Upload private durable reference material that the website agent can search, read, and inspect. - name: Analytics description: >- Read first-party traffic analytics for a website and export datasets as CSV. - name: Organizations description: Manage organizations, members, and organization-wide invitations. - name: Audit log description: >- Read the immutable record of actions performed in an organization by users and API keys. - name: Billing description: >- Read billing state and manage plans, site capacity, and prepaid usage balance. Every billing operation requires the organization owner role, which API keys cannot hold — today these operations are performed from the dashboard, return 403 for API-key callers, and are hidden from MCP tool lists. paths: /cms/collections/{collectionId}/items: post: tags: - CMS items summary: Create an item description: >- Creates an item at the end of the collection’s manual order. Scalar values go in `data` keyed by field key and are validated against the field types — unknown keys are rejected, required fields must be present, `plain_text` and `markdown` are capped at 1,048,576 bytes (markdown must not contain raw HTML), `date` values are ISO 8601 with timezone, and `color` values are normalized to hex. Relationship and asset values go in the side maps: `references` (`reference`: an item id; `multi_reference`: an ordered array of up to 1,000 ids), `images` (`image`: an asset id or `{ assetId, altText }`; `gallery`: an ordered array of up to 25 of those), and `files` (`file`: an asset id or `{ assetId }`). `slug` is optional — it is derived from `data.title` or `data.name` when omitted. Set a non-future `publishedAt` to create an already-published item, or a future `publishAt` to schedule it; the two fields are mutually exclusive. operationId: cms.items.create parameters: - name: collectionId in: path required: true schema: type: string minLength: 1 requestBody: required: false content: application/json: schema: type: object properties: slug: type: string pattern: ^[a-z0-9][a-z0-9-]{0,255}$ publishedAt: description: >- Initial publication timestamp. Must not be in the future. Omit for a draft, or use `publishAt` to schedule publication. anyOf: - {} - type: 'null' publishAt: description: >- Future absolute timestamp for scheduled publication. Cannot be combined with `publishedAt`. anyOf: - {} - type: 'null' data: default: {} type: object propertyNames: type: string additionalProperties: {} references: type: object propertyNames: type: string additionalProperties: anyOf: - type: string minLength: 1 - maxItems: 1000 type: array items: type: string minLength: 1 - type: 'null' images: type: object propertyNames: type: string additionalProperties: anyOf: - anyOf: - type: string minLength: 1 - type: object properties: assetId: type: string minLength: 1 altText: anyOf: - type: string maxLength: 2000 - type: 'null' required: - assetId additionalProperties: false - maxItems: 25 type: array items: anyOf: - type: string minLength: 1 - type: object properties: assetId: type: string minLength: 1 altText: anyOf: - type: string maxLength: 2000 - type: 'null' required: - assetId additionalProperties: false - type: 'null' files: type: object propertyNames: type: string additionalProperties: anyOf: - anyOf: - type: string minLength: 1 - type: object properties: assetId: type: string minLength: 1 required: - assetId - type: 'null' responses: '200': description: >- Identity of the created item. Read the full item back with the get-item endpoint. content: application/json: schema: type: object properties: id: type: string description: Id of the created item. slug: type: string description: >- Slug of the created item, derived from `data.title` or `data.name` when not provided. publishedAt: anyOf: - type: string format: date-time - type: 'null' description: >- `null` when the item was created as a draft; the publish timestamp otherwise. publishAt: anyOf: - type: string format: date-time - type: 'null' description: >- Future publication time when the item was created as scheduled; `null` otherwise. required: - id - slug - publishedAt - publishAt additionalProperties: false '400': description: >- Validation failed. The response `message` names the first invalid field. content: application/json: schema: $ref: '#/components/schemas/ServiceError' '401': description: Missing, invalid, expired, or revoked API key. content: application/json: schema: $ref: '#/components/schemas/ServiceError' '403': description: The authenticated principal lacks the required capability. content: application/json: schema: $ref: '#/components/schemas/ServiceError' '404': description: >- The resource does not exist or is outside the principal’s access scope. content: application/json: schema: $ref: '#/components/schemas/ServiceError' '409': description: The request conflicts with the current state of the resource. content: application/json: schema: $ref: '#/components/schemas/ServiceError' '429': description: >- Rate limit exceeded. Retry after the number of seconds in the `Retry-After` header. content: application/json: schema: $ref: '#/components/schemas/ServiceError' components: schemas: ServiceError: type: object required: - kind - message description: >- Canonical error body returned by every non-2xx response. Extra fields carry error-specific details. properties: kind: type: string enum: - validation - unauthorized - forbidden - not_found - conflict - rate_limited - internal description: Stable, machine-readable error category. message: type: string description: Human-readable explanation of the failure. suggestion: type: string description: >- What to do next when the failure has a known fix; may name the exact operation to call. validValues: type: array items: type: string description: The acceptable values for the failing field, when the set is closed. additionalProperties: true securitySchemes: apiKey: type: http scheme: bearer description: >- Cactal API key. Create one in the dashboard or via `POST /apiKeys`. The plaintext key is shown once at creation. ````