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:
Note: The modificationDate is automatically updated to the current timestamp
when any field is changed.
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.
Input for partially updating an information request. Only provided fields will be updated; omitted fields remain unchanged. At least one field must be provided.
The framework codes this request addresses. An empty array if no framework codes are associated.
Detailed description of what evidence is needed.
Deadline for fulfilling this request. Null if no deadline. Format: ISO 8601 UTC timestamp.
Start date of the audit period. Evidence before this date may not be accepted. Null if not restricted. Format: ISO 8601 UTC timestamp.
Scope of evidence required.
POINT_IN_TIME, POPULATION, SAMPLE Short, descriptive title.
How frequently this request recurs.
ANNUALLY, BIANNUALLY, MONTHLY, QUARTERLY 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.
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")
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.
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.
Current approval status tracking the request's lifecycle through evidence submission and auditor review.
NEEDS_EVIDENCE, READY_FOR_AUDIT, AUDITOR_APPROVED, AUDITOR_FLAGGED How frequently this information request recurs (e.g., annual password policy reviews). Null for one-time requests.
ANNUALLY, BIANNUALLY, MONTHLY, QUARTERLY 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.
Detailed description explaining what evidence is needed and why. Should provide clear instructions to help the customer understand what to submit.
The deadline by which the customer must fulfill this request. Null if no specific deadline is set. Format: ISO 8601 UTC timestamp.
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.
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.
Defines the scope of evidence required.
POINT_IN_TIME, POPULATION, SAMPLE Short, descriptive title summarizing what is being requested.
Timestamp when the request was created in the system. Format: ISO 8601 UTC timestamp.
Timestamp when the request was last modified. Format: ISO 8601 UTC timestamp.
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.
Resource owner (user or team) assigned to this information request. Returns null if no resource owner is assigned.