---
title: "Get Chunk By Tracking Id"
method: GET
path: "/api/chunk/tracking_id/{tracking_id}"
tags: ["Chunk"]
---

# Get Chunk By Tracking Id

`GET /api/chunk/tracking_id/{tracking_id}`

Get a singular chunk by tracking_id. This is useful for when you are coordinating with an external system and want to use your own id as the primary reference for a chunk.

## Path parameters

- `tracking_id` string, required

## Headers

- `TR-Dataset` string, uuid, required
- `X-API-Version` 'V1' | 'V2'

## Response `200`

chunk with the tracking_id that you were searching for

- union
  - ChunkMetadata
    - `chunk_html` string, nullable — HTML content of the chunk, can also be an arbitrary string which is not HTML
    - `created_at` string, date-time, required — Timestamp of the creation of the chunk
    - `dataset_id` string, uuid, required — ID of the dataset which the chunk belongs to
    - `id` string, uuid, required — Unique identifier of the chunk, auto-generated uuid created by Trieve
    - `image_urls` string[], nullable — Image URLs of the chunk, can be any list of strings. Used for image search and RAG.
    - `link` string, nullable — Link to the chunk, should be a URL
    - `location` GeoInfo — Location that you want to use as the center of the search.
      - `lat` union, required
        - integer
        - number, double
      - `lon` union, required
        - integer
        - number, double
    - `metadata` unknown
    - `num_value` number, double, nullable — 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.
    - `tag_set` string[], nullable — Tag set of the chunk, can be any list of strings. Used for tag-filtered searches.
    - `time_stamp` string, date-time, nullable — Timestamp of the chunk, can be any timestamp. Specified by the user.
    - `tracking_id` string, nullable — 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.
    - `updated_at` string, date-time, required — Timestamp of the last update of the chunk
    - `weight` number, double, required — Weight of the chunk, can be any float. Used as a multiplier on a chunk's relevance score for ranking purposes.
  - ChunkMetadataStringTagSet
    - `chunk_html` string, nullable
    - `created_at` string, date-time, required
    - `dataset_id` string, uuid, required
    - `id` string, uuid, required
    - `image_urls` string[], nullable
    - `link` string, nullable
    - `location` GeoInfo — Location that you want to use as the center of the search.
      - `lat` union, required
        - integer
        - number, double
      - `lon` union, required
        - integer
        - number, double
    - `metadata` unknown
    - `num_value` number, double, nullable
    - `tag_set` string, nullable
    - `time_stamp` string, date-time, nullable
    - `tracking_id` string, nullable
    - `updated_at` string, date-time, required
    - `weight` number, double, required

## Other responses

- `400` — Service error relating to fidning a chunk by tracking_id
- `404` — Chunk not found

---

[API](https://skmtc.net/devflowinc/apis/trieve-api.md) · [All operations](https://skmtc.net/devflowinc/apis/trieve-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/devflowinc/trieve-api/revisions/84583e7c9fc1/schema)