List code changes for an audit
Retrieves code changes population data for an audit.
This endpoint provides access to code change records (pull requests) visible to auditors during an audit engagement.
Supports filtering by:
- search: Searches code change titles and repository names (case-insensitive)
- sourcesMatchesAny: Filters by version control source (accepted values: github, gitlab, bitbucket, azuredevops)
- closedAfterDate / closedBeforeDate: Filters by the closed date range
Uses cursor-based pagination. To paginate:
- Make initial request with desired pageSize
- Check results.pageInfo.hasNextPage
- Use results.pageInfo.endCursor as pageCursor for next request
Results are sorted by closed date (newest first). This sort order is fixed and cannot be customized via query parameters.
Rate limit: 10 requests / minute.
Path parameters
The audit ID
Query parameters
Controls the maximum number of items returned in one response from the API.
Maximum number of results per page (1-100, default 10)
A marker or pointer, telling the API where to start fetching items for the subsequent page in a paginated dataset. Note that the requested page will not include the item that corresponds to this cursor but will start from the one immediately after this cursor.
Pagination cursor from previous response
Search term for filtering by code change title or repository name
Filter code changes by version control source (accepted values: github, gitlab, bitbucket, azuredevops)
Filter code changes closed on or after this date (ISO 8601)
Filter code changes closed on or before this date (ISO 8601)
Response
Paginated list of code changes with pagination metadata
Example response
{
"results": {
"data": [
{
"id": "5f2c939a52855e725c8d5824",
"codeChange": "fix-auth-bug",
"identifier": "101",
"service": "github",
"repository": "vanta/obsidian",
"openedAt": "2025-01-25T14:30:00.000Z",
"closedAt": "2025-03-25T14:30:00.000Z"
}
]
}
}