Status: Planned for future release. Not yet implemented.
Re-submit an already-processed document for a fresh compliance evaluation. Planned Endpoint: POST /v1/documents/{documentId}/reanalyze (Company Key) 
Option A: Re-analyze same document (planned endpoint):
  Partner ──POST /v1/documents/{documentId}/reanalyze──> API
         <── 200 OK { documentId, status: "Pending", controlItemCount, message }

Option B: Upload revised document (works today):
  Partner ──POST /v1/documents/submit──> API
         (complianceReviewId: "{existingReviewId}", files: [revised-policy.pdf])
         <── 200 OK { new documentId, same complianceReviewId }
  Then poll status + fetch results as usual.
Intended request fields:
FieldTypeDescription
selectedControlItemIdsstring[]Optional — re-analyze specific controls only. Omit to re-analyze all
Intended response (200): 
{
  "documentId": "01HXYZ...",
  "status": "Pending",
  "controlItemCount": 15,
  "message": "Re-analysis initiated"
}
Key design notes:
  • Option A (dedicated endpoint) is the planned approach — avoids re-uploading the same file
  • Option B (append revised doc) already works today via the existing submit flow
  • Re-analysis follows the same submission flow
  • Previous results will be preserved (versioned) for before/after comparison