Extract content from source documents, ingest, and orchestrate document generation using a template. Request is immediately queued as a background task and returns 202 Accepted. Poll /api/v1/documents/status/{document_id} for progress.
Field aliases (both forms accepted):
connector_data_id = document_set_keytemplate_id = generic_mrt_idworkspace_name = document_set_nameBearer token authentication. Token provides organization-scoped access.
Field aliases: connector_data_id = document_set_key, template_id = generic_mrt_id, workspace_name = document_set_name. Both the alias and field name are accepted.
Type of document to generate (e.g., CSR, Protocol)
S3 object keys for source documents (e.g., org-id/documents/protocol.pdf)
Unique key for document set (field name: document_set_key)
Human-readable name for the document set (field name: document_set_name)
ID of the template to use (field name: generic_mrt_id)
Name for the generated output file (without .docx extension)
Specific section IDs to include (optional)
Full outline structure (optional)
Document-level instructions (optional)
Style guide ID from the style_guides table (optional)