I need to include sources for my knowledge base files. Where in the file structure do you recommend | ElevenLabs | Page 1

AI-generated Answer for klara_56475

Short answer: ElevenLabs doesn’t document a recommended “place” inside your files for sources/citations. The publicly documented chunk API only exposes id, name, and content for each retrieved chunk, and there’s no documented per‑chunk metadata field for citations or a guarantee that references located elsewhere in the file (e.g., a bibliography section) will be associated with a chunk.

What is documented

Chunk shape: GET /v1/convai/knowledge-base/:documentation_id/chunk/:chunk_id returns only id, name, content. No citation/metadata fields are documented. (elevenlabs.io)
Document-level info you can rely on: GET /v1/convai/knowledge-base/:documentation_id returns type (file/url/text), url (for URL docs), name, and folder_path (if used). This is the level at which source attribution is exposed. (elevenlabs.io)
Original file retrieval: GET /v1/convai/knowledge-base/:documentation_id/source-file-url provides a signed URL to the original source file; again, this is document-level, not chunk-level. (elevenlabs.io)
General KB guidance: The docs advise clear structure and breaking large docs into smaller, focused pieces, but do not prescribe where to put citations within a file. (elevenlabs.io)

Implication

Because only chunk content is returned and there’s no documented per‑chunk citation metadata, the documentation does not guarantee preservation or association of a separate “sources” section during chunking. Manage attribution at the document level (names, URLs, folders) and, if needed, keep the original file accessible via the source-file-url endpoint. (elevenlabs.io)

If you need more granular, per‑passage citations, the official docs don’t describe a way to attach or retrieve that today. (elevenlabs.io)

#I need to include sources for my knowledge base files. Where in the file structure do you recommend