# Document Types Document Types (internally called **kinds**) define the categories of content that exist in your organization — controlling how documents are classified, displayed, and processed by downstream services. Every document must declare a kind at creation time. Kinds have a **KindType** classification that describes their primary role: | KindType | Description | |---|---| | `ASSET` | Represents a binary file or media asset (images, video, documents) | | `REFERENCE` | Represents a business entity that other documents relate to (brands, campaigns) | | `COLLECTION` | Groups related documents together (categories, playlists) | | `LAYOUT` | Structures content for presentation (toolkits, sections, blocks) | | `OTHER` | Custom or unclassified kind | **Platform-provided default kinds:** | Kind | KindType | Description | |---|---|---| | `media` | `ASSET` | Represents assets that originate from external channels (images, video, files). Linked to binary content, brands, campaigns, and source channel. | | `brand` | `REFERENCE` | Organizational brand entity. Links to a logo and splash image. Fields: `name`, `description`, `fgColor`, `bgColor`. | | `campaign` | `REFERENCE` | Marketing campaign. Links to brands and splash images. Fields: `title`, `description`, `brief`, `start`, `end`. | | `category` | `COLLECTION` | Dynamically generated content groupings. Supports subcategory hierarchies. Fields: `name`, `label`, `description`, `versionNumber`, `depth`, `isLatest`, `keywords`. | | `toolkit` | `LAYOUT` | Groups sections of content representing a brand identity. Links to sections and a parent brand. | | `section` | `LAYOUT` | Page layout element holding multiple blocks. Links to a toolkit, parent section, and child blocks. | | `block` | `LAYOUT` | Page element holding rich text and media. Links to media items. | Kinds are organized into **groups** for display in the platform UI (e.g., "Media Assets", "Creative Briefs"). Use `list-default-groups` to retrieve platform-defined groupings. Custom kinds can be created to extend this model for organization-specific content structures. Kinds work in conjunction with [Document Schemas](#tag/Document-Schemas), which define the metadata field structure and validation rules applied to documents of a given kind. ## Get document types - [POST /api/v1/kind/retrieve-kind](https://api.tenovos.com/openapi/content-intelligence/document-types/tenovos.document.kindservice.retrievekind.md): Retrieves full Kind definitions for one or more kind names, including trait definitions and schema ID. Request: kinds - List of Kind names to retrieve. Response: kinds - List of Kind objects each containing kind name, KindType, trait definitions, schemaId, optional description, and timestamps. ## Search document types - [POST /api/v1/kind/list-kind](https://api.tenovos.com/openapi/content-intelligence/document-types/tenovos.document.kindservice.listkind.md): Lists all Kind definitions as lightweight summaries with optional cursor-based pagination. Request: pagination - Optional Pagination cursor and page size. Response: kinds - List of KindSummary objects (kind name, type, schemaId, description, timestamps). pageCursor - Opaque cursor for the next page. Absent when there are no further results. ## Create a document type - [POST /api/v1/kind/create-kind](https://api.tenovos.com/openapi/content-intelligence/document-types/tenovos.document.kindservice.createkind.md): Creates one or more document type definitions. Each kind establishes a category of content in your organization and declares which capabilities (traits) documents of that type support. Request: kinds - List of kind definitions to create. Each includes: kind - Unique kind name (lowercase letters and underscores, 3–62 characters). type - Classifies the kind's role: ASSET (binary files and media), REFERENCE (business entities such as brands or campaigns), COLLECTION (groupings of related documents), LAYOUT (presentation structures such as pages or sections), or OTHER. traits - Capabilities this kind supports. Available traits: SUMMARY (name and description), TILE (visual card display), CONTENT (linked binary file), PREVIEW (renderable thumbnail), CHILDREN (parent-child document hierarchy), INSIGHTS (engagement analytics), TIMELINE (start and end dates), VERSION (revision tracking), and SOURCE (originating content channel). description - Optional human-readable description of the kind. schema - Optional inline metadata schema to attach at creation. groupId - Optional ID to associate the new kinds with a platform-defined template group. Response: kinds - Summary of each created kind, including its assigned ID and configuration. ## Update a document type - [POST /api/v1/kind/update-kind](https://api.tenovos.com/openapi/content-intelligence/document-types/tenovos.document.kindservice.updatekind.md): Updates the trait definitions and/or description for one or more existing Kinds. Request: kinds - List of update payloads. Each includes: kind - Name of the Kind to update. traits - Replacement list of TraitDefinition objects. description - Optional new description. Response: kinds - List of kind names that were successfully updated. ## Delete a document type - [POST /api/v1/kind/delete-kind](https://api.tenovos.com/openapi/content-intelligence/document-types/tenovos.document.kindservice.deletekind.md): Permanently deletes one or more Kind definitions by kind name. Request: kinds - List of Kind names to delete. Response: kinds - List of kind names that were successfully deleted. ## Get default groups for types - [POST /api/v1/kind/list-default-groups](https://api.tenovos.com/openapi/content-intelligence/document-types/tenovos.document.kindservice.listdefaultgroups.md): Returns the set of system-defined default Kind groups, each with their associated Kind summaries. Request: (no parameters) Response: groups - List of Group objects, each containing a groupId and a list of KindSummary objects belonging to that group. Used to seed default kinds when onboarding a new organization.