> ## Documentation Index > Fetch the complete documentation index at: https://developers.lighton.ai/llms.txt > Use this file to discover all available pages before exploring further. # Browse content-type starter templates > Browse the platform's **starter-kit templates** for content types. These are ready-made taxonomies (legal, finance, healthcare, tech, manufacturing) you can adopt to quickly organise your documents, no manual setup required. **Getting started:** 1. Browse templates here to see what's available 2. Adopt the ones you need: `POST /api/v3/content-types {"action": "adopt", "paths": ["legal", "finance"]}` 3. Once adopted, they become **your company's own** content types, fully editable 4. Customize: rename nodes, add children, define new attributes, or delete what you don't need 5. Create entirely new content types from scratch with `define_content_type` All write operations happen on `POST /api/v3/content-types`. This endpoint is read-only: it shows the catalog of available templates. **After adoption**, manage your company's content types (adopted + custom) via `GET /api/v3/content-types` and `POST /api/v3/content-types`. Classify files with `POST /api/v3/files/{id}/facets`. **Query modes:** - No params → full detail for all templates (children + attributes) - `?path=legal` → detail for one template - `?path=legal,finance` → detail for multiple (comma-separated) - `?path=legal:contract:nda` → detail for a nested node - `?depth=0` → root info only (code, label, description, no children/attributes) - `?depth=1` → roots + direct children only - `?include_attributes=false`: omit attribute definitions for a lighter response **Path separator:** `:` (colon). Example: `legal:contract:nda` **Attribute inheritance:** Attributes defined at a parent node are inherited by all its children. A document classified as `legal:contract:nda` gets attributes from `legal`, `legal:contract`, and `legal:contract:nda`. ## OpenAPI ````yaml /api-reference/api-console.yaml get /api/v3/content-types/templates openapi: 3.1.0 info: title: LightOn API version: 3.12.0 (v1) description: >- LightOn gives you an API to search, parse, and ingest documents at scale. Build knowledge-retrieval pipelines without managing vector databases or OCR models. servers: - url: https://api.lighton.ai security: [] tags: - name: Ask description: >- Retrieval-augmented generation: search your indexed corpus and generate an LLM answer grounded in the retrieved passages. Supports streaming (SSE) and synchronous modes. - name: Search description: >- Hybrid vector + text retrieval over your indexed corpus. Returns ranked passages with provenance (file, page range, workspace). Optional reranking and vision mode. - name: Files description: Upload, list, fetch, and delete documents indexed in your workspaces. - name: Facets description: >- Organise documents with hierarchical content types and custom attributes per file. Start from starter templates or build your own classification schema from scratch. - name: Tags description: >- Manage flat, company-wide labels used to scope search and group content across workspaces. - name: Workspaces description: >- Create and manage workspaces — the access-controlled containers your documents live in. - name: Parse description: >- Convert documents into structured Markdown — PDFs, images, Office files, and HTML. Synchronous endpoint capped at 20 MB / 15 pages. - name: Extract description: >- Pull typed fields out of documents using a JSON Schema you provide. Sync mode for small documents (≤20 MB / 15 pages); async mode for larger jobs (≤100 MB / 1000 pages) with polling on a job ID. - name: API Keys description: >- Provision and revoke API keys used to authenticate against the Console API. - name: Budget description: >- Manage your organization's monthly spend budget and alert thresholds. Set a hard cap that blocks API requests when reached, and configure email notifications at custom spend percentages. paths: /api/v3/content-types/templates: get: tags: - Facets summary: Browse content-type starter templates description: >- Browse the platform's **starter-kit templates** for content types. These are ready-made taxonomies (legal, finance, healthcare, tech, manufacturing) you can adopt to quickly organise your documents, no manual setup required. **Getting started:** 1. Browse templates here to see what's available 2. Adopt the ones you need: `POST /api/v3/content-types {"action": "adopt", "paths": ["legal", "finance"]}` 3. Once adopted, they become **your company's own** content types, fully editable 4. Customize: rename nodes, add children, define new attributes, or delete what you don't need 5. Create entirely new content types from scratch with `define_content_type` All write operations happen on `POST /api/v3/content-types`. This endpoint is read-only: it shows the catalog of available templates. **After adoption**, manage your company's content types (adopted + custom) via `GET /api/v3/content-types` and `POST /api/v3/content-types`. Classify files with `POST /api/v3/files/{id}/facets`. **Query modes:** - No params → full detail for all templates (children + attributes) - `?path=legal` → detail for one template - `?path=legal,finance` → detail for multiple (comma-separated) - `?path=legal:contract:nda` → detail for a nested node - `?depth=0` → root info only (code, label, description, no children/attributes) - `?depth=1` → roots + direct children only - `?include_attributes=false`: omit attribute definitions for a lighter response **Path separator:** `:` (colon). Example: `legal:contract:nda` **Attribute inheritance:** Attributes defined at a parent node are inherited by all its children. A document classified as `legal:contract:nda` gets attributes from `legal`, `legal:contract`, and `legal:contract:nda`. operationId: api_v3_content_types_templates_retrieve parameters: - in: query name: depth schema: type: integer description: >- Tree depth limit. Default (omitted) = full tree. `0` = root info only (no children, no attributes). `1` = roots + direct children. `N` = N levels of children. - in: query name: include_attributes schema: type: boolean description: 'Include attribute definitions per content type node. Default: true.' - in: query name: path schema: type: string description: >- Content type path(s), colon-separated hierarchy. Comma-separated for multiple (e.g., `?path=legal,finance`, `?path=tech,manufacturing`, or `?path=legal:contract:nda`). Root codes: finance, healthcare, legal, manufacturing, tech examples: LegalRoot: value: legal summary: Legal root description: Get the full legal content type tree HealthcareRoot: value: healthcare summary: Healthcare root description: Get the full healthcare content type tree FinanceRoot: value: finance summary: Finance root description: Get the full finance content type tree TechRoot: value: tech summary: Tech root description: Get the full tech content type tree ManufacturingRoot: value: manufacturing summary: Manufacturing root description: Get the full manufacturing content type tree NestedNode: value: legal:contract:nda summary: Nested node description: Get detail for a specific leaf node responses: '200': description: Content types returned successfully '401': content: application/json: schema: $ref: '#/components/schemas/APIV3ErrorResponse' examples: Unauthorized: value: id: null code: 401 error: unauthorized detail: >- Authentication credentials were not provided or are invalid. doc_url: https://developers.lighton.ai/errors#unauthorized description: Authentication credentials were not provided or are invalid '404': description: Content type path(s) not found security: - bearerAuth: [] components: schemas: APIV3ErrorResponse: type: object properties: id: type: - string - 'null' description: >- Job/resource id when one already exists (useful for async error diagnosis); null otherwise. code: type: integer description: HTTP status code error: type: string description: Error code used by the UI as a translation key detail: type: string description: Human-readable error message for developers doc_url: type: string description: Link to the error-code documentation page required: - code - detail - doc_url - error - id securitySchemes: bearerAuth: type: http scheme: bearer description: >- Bearer authentication header of the form `Bearer `, where `` is your auth token. ````