Flag evidence for an information request
Flags evidence for an information request when it doesn’t meet audit requirements, marking issues that need to be addressed before approval. This action changes the request’s approvalStatus to a flagged state and creates an activity log entry.
Flagging workflow:
- Auditor reviews submitted evidence
- If issues are found, auditor calls this endpoint with detailed reason
- Request status changes to flagged state
- Customer is notified and can see the reason in activity logs
- Customer addresses issues and updates evidence
- When ready, customer changes status back to awaiting review
- Auditor reviews again and either flags again or accepts
The reason field should clearly explain what’s missing or incorrect so the
customer knows exactly what to fix. This reason is visible to the customer
and appears in the activity log.
Rate limit: 50 requests / minute.
Authorizations
Body
Input for flagging evidence on an information request, indicating issues that need to be addressed. This changes the request's approvalStatus to a flagged state and creates an activity log entry.
The customer will be notified and can resubmit evidence after addressing the issues.
Response
Ok
Information Request resource representing a single request for audit evidence from a customer.
An information request is created by an auditor and shared with the customer organization. The customer then uploads evidence, which the auditor reviews and either approves or flags for issues.
Deprecated control-linkage field retained for response compatibility. It
may contain control IDs supplied directly to the request, but it is not a
complete or guaranteed-current list of controls linked to the request. Use
linkedControlIds for the complete current list.
Audit segments this request is assigned to. Empty means unassigned. Resolved against the current audit scope — stale IDs are dropped.
This field is a current-scope projection, not a stored watermark. An
audit-scope change that drops or adds IDs here does not update
creationDate, modificationDate, or deletionDate, so it does not appear in
changedSinceDate delta sync on its own. Re-fetch the list without that
parameter, or GET the request by id, to see the current projection.