Evidence status changed
Fires when an existing audit evidence item changes status. oldStatus and newStatus always describe a transition of an item that already exists. See v1.evidence.created for the event that fires when an item first comes into scope for an audit.
Ready-to-review signal: a newStatus of READY_FOR_AUDIT means the customer has provided evidence for the item and it is ready for the auditor to review.
When it fires: once per evidence item, each time its status changes. Status can also change on its own as the customer’s compliance posture changes, so an item may move from READY_FOR_AUDIT back to NOT_READY_FOR_AUDIT without an explicit auditor action.
oldStatus and newStatus can be equal. A newly detected document re-fires this event with both fields set to the item’s current status (for example, READY_FOR_AUDIT, ACCEPTED, or FLAGGED). Treat that as a signal that the item’s files may have changed and re-fetch its URLs. Do not discard events where the status is unchanged.
Status values:
NOT_READY_FOR_AUDIT— the item is not yet ready for the auditor; required evidence is missing or does not meet the requirement.READY_FOR_AUDIT— the customer has provided the evidence and it is ready for the auditor to review.ACCEPTED— the auditor reviewed the item and accepted it.FLAGGED— the auditor reviewed the item and flagged an issue for the customer to address; once the customer addresses it the item returns toREADY_FOR_AUDIT.NA— the item is not applicable to this audit.
A typical lifecycle is NOT_READY_FOR_AUDIT → READY_FOR_AUDIT → ACCEPTED (or → FLAGGED, which returns to READY_FOR_AUDIT once the customer addresses the issue). INITIALIZED is an internal status and is never delivered — oldStatus and newStatus are always one of the values above.
Body
Response
Return any 2xx status within 15 seconds to acknowledge receipt.
Related topics
Evidence createdVanta API changelogInformation request status changedQuestionnaire status changedList audit evidence