---
title: "Get a record's full parsed content and metadata"
method: GET
path: "/connectors/record/{recordId}/content"
tags: ["Connector"]
---

# Get a record's full parsed content and metadata

`GET /connectors/record/{recordId}/content`

Retrieve the full parsed content and metadata of a single record —
the same content PipesHub's own RAG/chat pipeline uses to answer
questions, returned directly instead of via chat.

**When to use this vs. the other record endpoints:**
- `GET /knowledgeBase/record/{recordId}` returns metadata only
  (name, type, indexing status, size) — no content.
- `GET /knowledgeBase/stream/record/{recordId}` returns the original,
  unparsed file bytes — use it to download/open the source file.
- **This endpoint** returns the record's full parsed content as a
  single plain-text `content` string (a metadata header, then the
  block/table text in reading order, then any foreign-key related
  tables) — use it when you need the record's actual textual/tabular
  content without downloading and re-parsing the original file yourself.

**Typical flow:** obtain a `recordId` from a `pipeshub_search` hit or
a chat citation's `recordId`, then call this endpoint to read the
full content when the search snippet or citation excerpt isn't
enough to answer the question.

**Permission scoping:**

The requesting user/token must have access to the record; access is
verified via the knowledge graph before content is returned — a
caller with a valid scope but no access to this specific record gets
a `403`.

## Path parameters

- `recordId` string, required

## Response `200`

Successful operation. When the record has no available content
(e.g. not indexed), `content` is the literal `No record found`
rather than an error status.

- GetRecordContentResponseSchema — Response returned by GET /connectors/record/{recordId}/content. `content` is the record's full parsed content flattened into a single plain-text string: a metadata header (title, source, key fields, and a short summary), then the record's block/table text in reading order, and finally a foreign-key related-tables footer for `SQL_TABLE` records. For `TICKET` records (e.g. Jira) the metadata header is refreshed with live ticket fields (status, assignee, comments) at request time rather than the last-indexed snapshot. `content` may be empty for records with no extractable text (e.g. image-only or not-yet-parsed records).
  - `content` string, required — The record's full parsed content as a single plain-text string.

## Other responses

- `401` — Missing, invalid, expired, or revoked authentication
- `403` — OAuth token is missing the `connector:read` scope, or the authenticated user does not have access to this record.
- `500` — Internal server error while fetching record content
- `503` — Connector service unavailable or connection refused

---

[API](https://skmtc.net/pipeshub-ai/apis/pipeshub-api.md) · [All operations](https://skmtc.net/pipeshub-ai/apis/pipeshub-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pipeshub-ai/pipeshub-api/revisions/64bfe76b130e/schema)