Updates an existing comment for an information request. Only the original author of the comment can update it. The author is identified by their email address, which must match the email of the user who created the comment.
Documentation Index
Fetch the complete documentation index at: https://vanta.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Updates an existing comment on an information request. Only the original author of the comment can update it.
The text content of the comment. Must be at least 1 character. Can include questions, clarifications, or explanations related to the information request.
Email address of the comment author. Must match an existing Vanta user who belongs to the audit firm making the API request. This email uniquely identifies the author across systems.
Ok
A comment on an information request enables communication between auditors and customers regarding evidence requirements and submissions.
These threaded discussions help clarify requests, explain or resolve questions about evidence, and are always visible to both parties once created.
The unique identifier for the comment within Vanta's system. Format: ObjectId as a string (e.g., "6890e473dce1da5d8406f5e7").
The comment message content. Can include explanations, questions, or clarifications about the information request.
Timestamp when the comment was created. Format: ISO 8601 UTC timestamp.
Timestamp when the comment was last edited. Null if the comment has never been modified. Format: ISO 8601 UTC timestamp.
Timestamp when the comment was soft-deleted. Null if the comment has not been deleted. Soft deletes retain the comment for audit history while hiding it from normal operations. Format: ISO 8601 UTC timestamp.
Email address of the comment author. This email uniquely identifies users between Vanta and external audit systems.
Human-readable display name of the comment author. Null if the author's name is not available (e.g., user was deleted). This enables correct author attribution in integrations where users cannot be reliably matched across systems by email alone.