---
title: "Create a comment for audit evidence"
method: POST
path: "/audits/{auditId}/evidence/{auditEvidenceId}/comments"
tags: ["Audits"]
---

# Create a comment for audit evidence

`POST /audits/{auditId}/evidence/{auditEvidenceId}/comments`

Create a comment in Vanta for a piece of evidence.

Rate limit: 10 requests / minute.

## Path parameters

- `auditId` string, required
- `auditEvidenceId` string, required

## Request body

- AddCommentInput
  - `text` string, required — Text value of the comment
  - `email` string, required — Email of author. Must match an existing Vanta user and the user must exist under the Audit Firm who is making the API request
  - `creationDate` string, date-time, required — When the comment was created in the external system

## Response `200`

Ok

- Comment
  - `id` string, required — The unique identifier for the comment
  - `auditEvidenceId` string, required — The unique identifier for the audit evidence related to the comment.
  - `text` string, required — The comment message
  - `creationDate` string, date-time, required — When the comment was created
  - `modificationDate` string, date-time, nullable, required — When the comment was updated
  - `deletionDate` string, date-time, nullable, required — When the comment was deleted
  - `email` string, nullable, required — The email of the comment author. This acts as a unique identifier to map users between Vanta and external systems.
  - `authorName` string, nullable, required — 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.

---

[API](https://skmtc.net/vanta/apis/build-integrations.md) · [All operations](https://skmtc.net/vanta/apis/build-integrations/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/vanta/build-integrations/versions/6c1f7590538b/schema)