{"templateId":"openapi_docs","sharedDataIds":{"openAPIDocsStore":"oas-openapi/content-intelligence.yaml","sidebar":"sidebar-sidebars.yaml"},"props":{"definitionId":"openapi/content-intelligence.yaml","dynamicMarkdocComponents":[],"baseSlug":"/openapi/content-intelligence","seo":{"title":"Document Management","llmstxt":{"hide":false,"sections":[{"title":"Table of contents","includeFiles":["**/*"],"excludeFiles":[]}],"excludeFiles":[]},"description":"Documents are the primary data model in the Content Intelligence Platform. Each document is\na JSON object that holds metadata as flexible name/value pairs — there is no fixed schema\nenforced at the storage layer, which allows content from diverse external systems (DAMs,\ncloud storage, SharePoint, Box, etc.) to be ingested without transformation.\n\nDocuments exist within a graph-like structure where **nodes** (individual documents) and\n**edges** (links between documents) form a highly relational content model. For example,\na `media` document can be linked to a `campaign` document, enabling hierarchical queries\nand relationship traversal across the content graph.\n\n**Document traits** define behavioral capabilities of a document type:\n\n| Trait | Description |\n|---|---|\n| `SUMMARY` | Document has a displayable summary representation |\n| `CHILDREN` | Document can contain child documents |\n| `TILE` | Document can be displayed as a tile/card |\n| `CONTENT` | Document is linked to binary content (files) |\n| `PREVIEW` | Document can generate a visual preview |\n| `INSIGHTS` | Document tracks engagement analytics |\n| `TIMELINE` | Document has a temporal lifecycle (start/end dates) |\n| `VERSION` | Document supports versioning |\n| `SOURCE` | Document tracks its originating content channel |\n\n**Endpoint reference:**\n\n- `create` — create one or more documents of a given kind, with optional external ID for deduplication\n- `retrieve` — fetch a document by ID with full metadata and linked content references\n- `list` — paginated listing of documents, filtered by kind, status, or metadata values\n- `query` — full-text and field-level search across the document graph\n- `query-within` — scoped search within a specific document hierarchy (e.g., within a brand or campaign)\n- `link / unlink` — create or remove typed edges between documents (e.g., link media to a campaign)\n- `retrieve-links` — traverse outbound edges from a document to its related documents\n- `update` — modify document metadata fields; uses partial update (only supplied fields change)\n- `delete / undelete` — soft-delete with restore; deleted documents remain queryable with a filter\n- `purge` — permanently remove a document and all its edges\n- `reindex` — trigger re-indexing of a document into OpenSearch; use after bulk imports or schema changes\n\nDocuments reference binary content managed by the [Content Storage](#tag/Content-Storage) service\nand are typed using [Document Types](#tag/Document-Types) with optional schema enforcement\nvia [Document Schemas](#tag/Document-Schemas).\n"},"itemId":"document-management","disableAutoScroll":true,"metadata":{"subType":"openapi-operation"},"compilationErrors":[],"markdown":{"partials":{},"variables":{"rbac":{"teams":["anonymous"]},"user":{},"remoteAddr":{"hostname":"api.tenovos.com","port":4000,"ipAddress":"216.73.217.51"},"lang":"default_locale","env":{"PUBLIC_REDOCLY_BRANCH_NAME":"main"}}},"pagePropGetterError":{"message":"","name":""}},"slug":"/openapi/content-intelligence/document-management","userData":{"isAuthenticated":false,"teams":["anonymous"]},"isPublic":true}