latestOpenAPI 3.0.0raw.githubusercontent.com2026-08-1391215649.1 KB

64bfe76b130e

Connector

Get a record's full parsed content and metadata

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.

get/connectors/record/{recordId}/content

Path parameters

recordIdstring required

Record ID to fetch. Obtain it from a pipeshub_search result (hits[*].recordId) or a chat citation (citations[*].recordId).

Response

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.

contentstring required

The record's full parsed content as a single plain-text string.