> ## Documentation Index > Fetch the complete documentation index at: https://docs.trieve.ai/llms.txt > Use this file to discover all available pages before exploring further. # Split HTML Content into Chunks > This endpoint receives a single html string and splits it into chunks based on the headings and body content. The headings are split based on heading html tags. chunk_html has a maximum size of 256Kb. ## OpenAPI ````yaml post /api/chunk/split openapi: 3.0.3 info: title: Trieve API description: >- Trieve OpenAPI Specification. This document describes all of the operations available through the Trieve API. contact: name: Trieve Team url: https://trieve.ai email: developers@trieve.ai license: name: BSL url: https://github.com/devflowinc/trieve/blob/main/LICENSE.txt version: 0.13.0 servers: - url: https://api.trieve.ai description: Production server - url: http://localhost:8090 description: Local development server security: [] tags: - name: Invitation description: Invitation endpoint. Exists to invite users to an organization. - name: Auth description: Authentication endpoint. Serves to register and authenticate users. - name: User description: User endpoint. Enables you to modify user roles and information. - name: Organization description: >- Organization endpoint. Enables you to modify organization roles and information. - name: Dataset description: >- Dataset endpoint. Datasets belong to organizations and hold configuration information for both client and server. Datasets contain chunks and chunk groups. - name: Chunk description: >- Chunk endpoint. Think of chunks as individual searchable units of information. The majority of your integration will likely be with the Chunk endpoint. - name: Chunk Group description: >- Chunk groups endpoint. Think of a chunk_group as a bookmark folder within the dataset. - name: Crawl description: Crawl endpoint. Used to create and manage crawls for datasets. - name: File description: >- File endpoint. When files are uploaded, they are stored in S3 and broken up into chunks with text extraction from Apache Tika. You can upload files of pretty much any type up to 1GB in size. See chunking algorithm details at `docs.trieve.ai` for more information on how chunking works. Improved default chunking is on our roadmap. - name: Events description: >- Notifications endpoint. Files are uploaded asynchronously and events are sent to the user when the upload is complete. - name: Topic description: >- Topic chat endpoint. Think of topics as the storage system for gen-ai chat memory. Gen AI messages belong to topics. - name: Message description: >- Message chat endpoint. Messages are units belonging to a topic in the context of a chat with a LLM. There are system, user, and assistant messages. - name: Stripe description: >- Stripe endpoint. Used for the managed SaaS version of this app. Eventually this will become a micro-service. Reach out to the team using contact info found at `docs.trieve.ai` for more information. - name: Health description: Health check endpoint. Used to check if the server is up and running. - name: Metrics description: Metrics endpoint. Used to get information for monitoring - name: Analytics description: Analytics endpoint. Used to get information for search and RAG analytics - name: Experiment description: Experiment endpoint. Used to create and manage experiments paths: /api/chunk/split: post: tags: - Chunk summary: Split HTML Content into Chunks description: >- This endpoint receives a single html string and splits it into chunks based on the headings and body content. The headings are split based on heading html tags. chunk_html has a maximum size of 256Kb. operationId: split_html_content requestBody: description: JSON request payload to perform RAG on some chunks (chunks) content: application/json: schema: $ref: '#/components/schemas/ChunkHtmlContentReqPayload' required: true responses: '200': description: >- This will be a JSON response of the chunks split from the HTML content with the headings and body content: application/json: schema: $ref: '#/components/schemas/SplitHtmlResponse' '413': description: Payload too large, if the HTML contnet is greater than 256Kb content: application/json: schema: $ref: '#/components/schemas/ErrorResponseBody' components: schemas: ChunkHtmlContentReqPayload: type: object required: - chunk_html properties: body_remove_strings: type: array items: type: string description: Text strings to remove from body when creating chunks for each page nullable: true chunk_html: type: string description: The HTML content to be split into chunks heading_remove_strings: type: array items: type: string description: >- Text strings to remove from headings when creating chunks for each page nullable: true example: body_remove_strings: - 'Warning:' - 'Note:' chunk_html: '' heading_remove_strings: - '###' - '##' - '#' SplitHtmlResponse: type: object required: - chunks properties: chunks: type: array items: $ref: '#/components/schemas/ChunkedContent' example: chunks: - body: This is the body of the content headings: - Title Heading - Sub Heading 1 - Sub Sub Heading 1 - body: This is the body of the content headings: - Title Heading - Sub Heading 1 - Sub Sub Heading 2 ErrorResponseBody: type: object required: - message properties: message: type: string example: message: Bad Request ChunkedContent: type: object required: - headings - body properties: body: type: string description: The body of the content headings: type: array items: type: string description: The headings of the content in order of when they appear example: body: This is the body of the content headings: - Title Heading - Sub Heading 1 - Last SubHeading ````