---
title: "Read tracker items for use as a test-generation specification"
method: POST
path: "/issueTrackers/workspaces/{workspace_id}/items:content"
tags: ["TrackerItem"]
---

# Read tracker items for use as a test-generation specification

`POST /issueTrackers/workspaces/{workspace_id}/items:content`

The readable content of each item: a fixed set of fields chosen by the item's category, converted to plain text, with test case steps parsed into action and expected pairs. The integration must belong to this workspace and be enabled, and each item must lie in its configured project. Every item reports readable and a reason, so one bad item does not fail the request.

## Path parameters

- `workspace_id` string, required

## Request body

- TrackerItemContentRequest
  - `workspace_integration_id` string, required — The integration whose project holds these items. Item ids are unique only per organization, so the caller must say which; it is validated against the workspace.
  - `issue_keys` string[], required — Canonical keys, at most 5 -- each costs upstream calls and prompt budget

## Response `200`

One entry per requested key, in request order

- TrackerItemContentResult — One entry per requested key, in request order.
  - `items` TrackerItemContent[], required
    - `issue_key` string, required
    - `display_key` string, required
    - `readable` boolean, required
    - `reason` 'not_found' | 'not_in_project' | 'no_readable_content' | 'unavailable' | 'deadline' | 'rate_limited' | 'unsupported_platform' — not_found: the tracker has no such item, or it is not a valid key. not_in_project: the item lies outside the integration's configured project. no_readable_content: the item was read but holds nothing in the readable fields, or earlier items used the whole size budget (truncated is then true). unavailable: the tracker could not be asked. deadline: the request ran out of time before this item was read. rate_limited: the organization's request allowance is exhausted. unsupported_platform: the integration's tracker does not support reading items.
    - `title` string
    - `item_type` string
    - `state` string
    - `url` string
    - `sections` TrackerItemSection[] — Free-text fields as plain text, e.g. Description and Acceptance Criteria.
      - `label` string, required
      - `text` string, required
    - `steps` TrackerItemStep[] — Ordered test case steps, when the item has them.
      - `index` integer — 1-based position in the item.
      - `action` string
      - `expected` string
    - `truncated` boolean — Whether content was dropped to fit the size budget. A caller must not present a truncated item as fully covered.

## Other responses

- `400` — Invalid or missing parameter
- `401` — User not authenticated
- `402` — Unknown error
- `403` — User not authorized
- `default` — Unknown error

---

[API](https://skmtc.dev/mabl/apis/mabl-api.md) · [All operations](https://skmtc.dev/mabl/apis/mabl-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mabl/apis/mabl-api/revisions/24dd8c2933df?raw)