> ## 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. # Get Chunks By Ids > Get multiple chunks by multiple ids. ## OpenAPI ````yaml post /api/chunks 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/chunks: post: tags: - Chunk summary: Get Chunks By Ids description: Get multiple chunks by multiple ids. operationId: get_chunks_by_ids parameters: - name: TR-Dataset in: header description: >- The dataset id or tracking_id to use for the request. We assume you intend to use an id if the value is a valid uuid. required: true schema: type: string format: uuid - name: X-API-Version in: header description: >- The API version to use for this request. Defaults to V2 for orgs created after July 12, 2024 and V1 otherwise. required: false schema: allOf: - $ref: '#/components/schemas/APIVersion' nullable: true requestBody: description: JSON request payload to get the chunks in the request content: application/json: schema: $ref: '#/components/schemas/GetChunksData' required: true responses: '200': description: chunks with the id that you were searching for content: application/json: schema: type: array items: $ref: '#/components/schemas/ChunkReturnTypes' '400': description: Service error relating to fidning a chunk by tracking_id content: application/json: schema: $ref: '#/components/schemas/ErrorResponseBody' '404': description: Any one of the specified chunks not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponseBody' security: - ApiKey: - readonly components: schemas: APIVersion: type: string enum: - V1 - V2 GetChunksData: type: object required: - ids properties: ids: type: array items: type: string format: uuid ChunkReturnTypes: oneOf: - $ref: '#/components/schemas/ChunkMetadata' - $ref: '#/components/schemas/ChunkMetadataStringTagSet' ErrorResponseBody: type: object required: - message properties: message: type: string example: message: Bad Request ChunkMetadata: type: object title: V2 required: - id - created_at - updated_at - dataset_id - weight properties: chunk_html: type: string description: >- HTML content of the chunk, can also be an arbitrary string which is not HTML nullable: true created_at: type: string format: date-time description: Timestamp of the creation of the chunk dataset_id: type: string format: uuid description: ID of the dataset which the chunk belongs to id: type: string format: uuid description: >- Unique identifier of the chunk, auto-generated uuid created by Trieve image_urls: type: array items: type: string nullable: true description: >- Image URLs of the chunk, can be any list of strings. Used for image search and RAG. nullable: true link: type: string description: Link to the chunk, should be a URL nullable: true location: allOf: - $ref: '#/components/schemas/GeoInfo' nullable: true metadata: description: Metadata of the chunk, can be any JSON object nullable: true num_value: type: number format: double description: >- Numeric value of the chunk, can be any float. Can represent the most relevant numeric value of the chunk, such as a price, quantity in stock, rating, etc. nullable: true tag_set: type: array items: type: string nullable: true description: >- Tag set of the chunk, can be any list of strings. Used for tag-filtered searches. nullable: true time_stamp: type: string format: date-time description: Timestamp of the chunk, can be any timestamp. Specified by the user. nullable: true tracking_id: type: string description: >- Tracking ID of the chunk, can be any string, determined by the user. Tracking ID's are unique identifiers for chunks within a dataset. They are designed to match the unique identifier of the chunk in the user's system. nullable: true updated_at: type: string format: date-time description: Timestamp of the last update of the chunk weight: type: number format: double description: >- Weight of the chunk, can be any float. Used as a multiplier on a chunk's relevance score for ranking purposes. example: chunk_html:

Hello, world!

created_at: '2021-01-01 00:00:00.000' dataset_id: e3e3e3e3-e3e3-e3e3-e3e3-e3e3e3e3e3e3 id: e3e3e3e3-e3e3-e3e3-e3e3-e3e3e3e3e3e3 link: https://trieve.ai metadata: key: value tag_set: '[tag1,tag2]' time_stamp: '2021-01-01 00:00:00.000' tracking_id: e3e3e3e3-e3e3-e3e3-e3e3-e3e3e3e3e3e3 updated_at: '2021-01-01 00:00:00.000' weight: 0.5 ChunkMetadataStringTagSet: type: object title: V1 required: - id - created_at - updated_at - dataset_id - weight properties: chunk_html: type: string nullable: true created_at: type: string format: date-time dataset_id: type: string format: uuid id: type: string format: uuid image_urls: type: array items: type: string nullable: true nullable: true link: type: string nullable: true location: allOf: - $ref: '#/components/schemas/GeoInfo' nullable: true metadata: nullable: true num_value: type: number format: double nullable: true tag_set: type: string nullable: true time_stamp: type: string format: date-time nullable: true tracking_id: type: string nullable: true updated_at: type: string format: date-time weight: type: number format: double example: created_at: '2021-01-01 00:00:00.000' dataset_id: e3e3e3e3-e3e3-e3e3-e3e3-e3e3e3e3e3e3 id: e3e3e3e3-e3e3-e3e3-e3e3-e3e3e3e3e3e3 link: https://trieve.ai metadata: key: value tag_set: tag1,tag2 time_stamp: '2021-01-01 00:00:00.000' tracking_id: e3e3e3e3-e3e3-e3e3-e3e3-e3e3e3e3e3e3 updated_at: '2021-01-01 00:00:00.000' weight: 0.5 GeoInfo: type: object description: Location that you want to use as the center of the search. required: - lat - lon properties: lat: $ref: '#/components/schemas/GeoTypes' lon: $ref: '#/components/schemas/GeoTypes' GeoTypes: oneOf: - type: integer format: int64 - type: number format: double securitySchemes: ApiKey: type: apiKey in: header name: Authorization ````