---
title: "Update an information request for an audit"
method: PATCH
path: "/audits/{auditId}/information-requests/{requestId}"
tags: ["Audits"]
---

# Update an information request for an audit

`PATCH /audits/{auditId}/information-requests/{requestId}`

Updates an existing information request for an audit, allowing modification of request
details as audit requirements evolve. Supports partial updates where only specified
fields are changed; omitted fields remain unchanged.

Common use cases:
- Updating due dates as audit timelines shift
- Refining descriptions to clarify requirements
- Adjusting request type

Note: The `modificationDate` is automatically updated to the current timestamp
when any field is changed.

Rate limit: 50 requests / minute.

## Path parameters

- `auditId` string, required
- `requestId` string, required

## Request body

- PartialUpdateInformationRequest — Input for partially updating an information request. Only provided fields will be updated; omitted fields remain unchanged. At least one field must be provided.
  - `frameworkCodes` string[] — The framework codes this request addresses. An empty array if no framework codes are associated.
  - `description` string, nullable — Detailed description of what evidence is needed.
  - `dueDate` string, date-time, nullable — Deadline for fulfilling this request. Null if no deadline. Format: ISO 8601 UTC timestamp.
  - `evidenceCaptureDate` string, date-time, nullable — Start date of the audit period. Evidence before this date may not be accepted. Null if not restricted. Format: ISO 8601 UTC timestamp.
  - `requestType` 'POINT_IN_TIME' | 'POPULATION' | 'SAMPLE' — Type of information request, defining what scope of evidence is needed. - POINT_IN_TIME: Evidence for a specific moment (e.g., current state of a policy) - POPULATION: Evidence covering all items in a category (e.g., all employees) - SAMPLE: Evidence for a representative sample (e.g., 10 random customer records)
  - `title` string — Short, descriptive title.
  - `cadence` 'ANNUALLY' | 'BIANNUALLY' | 'MONTHLY' | 'QUARTERLY' — Frequency cadence for the information request, indicating how often it recurs.
  - `additionalControlIds` string[] — Control IDs to link directly to this request, beyond those automatically mapped from framework codes. Replaces the existing set: pass the complete desired list, an empty array to clear all direct control links, or omit to leave them unchanged. Each must be the `id` of an existing control in the customer's organization (the identifier returned by the controls endpoints). The request is rejected if any ID does not match a control.

## Response `200`

Ok

- InformationRequest — 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.
  - `id` string, required — The unique identifier for the information request within Vanta's system. This is the primary identifier used in all API endpoints. Format: ObjectId as a string (e.g., "6890e473dce1da5d8406f5e7")
  - `uniqueId` string, required — External unique ID to prevent duplicates across different audit systems. Used for idempotency when syncing data between external audit management systems and Vanta. Unlike `id`, this value is provided by the external system.
  - `additionalControlIds` string[], required — Additional control IDs beyond those automatically mapped from framework codes. Allows manual association with specific controls when automatic mapping is insufficient. Each ID should reference a valid control in your audit framework.
  - `approvalStatus` 'NEEDS_EVIDENCE' | 'READY_FOR_AUDIT' | 'AUDITOR_APPROVED' | 'AUDITOR_FLAGGED', required — Current approval status of the information request, tracking its lifecycle through the audit process. The status progresses through the workflow: initial state → awaiting review → approved or flagged. Status can move between awaiting review and flagged states as evidence is reviewed and resubmitted.
  - `cadence` 'ANNUALLY' | 'BIANNUALLY' | 'MONTHLY' | 'QUARTERLY', required — Frequency cadence for the information request, indicating how often it recurs.
  - `frameworkCodes` string[], required — The framework codes this request addresses. Links the request to specific compliance requirements. Can be an empty array if no framework codes are associated. These codes correspond to standards like SOC 2, ISO 27001, etc.
  - `description` string, nullable, required — Detailed description explaining what evidence is needed and why. Should provide clear instructions to help the customer understand what to submit.
  - `dueDate` string, date-time, nullable, required — The deadline by which the customer must fulfill this request. Null if no specific deadline is set. Format: ISO 8601 UTC timestamp.
  - `evidenceCaptureDate` string, date-time, nullable, required — The earliest date for which evidence should be captured. Evidence dated before this date may not be accepted. Null if not restricted. Format: ISO 8601 UTC timestamp.
  - `requestId` string, nullable, required — Non-unique external reference ID for this request. Unlike `uniqueId` which must be unique, `requestId` is for display/reference purposes only (e.g., "REQ-123"). Null if not provided.
  - `requestType` 'POINT_IN_TIME' | 'POPULATION' | 'SAMPLE', required — Type of information request, defining what scope of evidence is needed. - POINT_IN_TIME: Evidence for a specific moment (e.g., current state of a policy) - POPULATION: Evidence covering all items in a category (e.g., all employees) - SAMPLE: Evidence for a representative sample (e.g., 10 random customer records)
  - `title` string, required — Short, descriptive title summarizing what is being requested.
  - `creationDate` string, date-time, required — Timestamp when the request was created in the system. Format: ISO 8601 UTC timestamp.
  - `modificationDate` string, date-time, required — Timestamp when the request was last modified. Format: ISO 8601 UTC timestamp.
  - `deletionDate` string, date-time, nullable, required — Timestamp when the request was soft-deleted. Null if the request has not been deleted. Soft deletes allow retaining history while hiding the request from normal operations. Format: ISO 8601 UTC timestamp.
  - `ownerAssignment` union, required — Represents either a user or a team owning a resource.
    - object
      - `displayName` string, required
      - `id` string, required
      - `type` 'user', required
    - object
      - `displayName` string, required
      - `id` string, required
      - `type` 'team', required

---

[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)