templates
Get Attachment Content
The attachment's CURRENT working text — what's actually indexed and served to the agent — as opposed to file_url, which always points at the original upload and never reflects edits (corrections, open-question answers, and the audit loop all write to extracted_text, not the source file). This is the only way for a template author to visually verify an edit landed: downloading file_url shows the pristine original forever, by design (see attachment_processor / document_indexer — the S3 object is provenance, extracted_text is the live document).
get/v1/templates/{template_id}/attachments/{attachment_id}/content
Path parameters
template_idstring required
attachment_idstring required
Response
Successful Response
{"stackTrail":"paths:/v1/templates/{template_id}/attachments/{attachment_id}/content:get:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}
Changes
No recorded changes to this endpoint across all 1 revision of this API.