docs: add API audit logs and CSV export page#290
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the new streaming CSV export for project API audit logs, plus the existing audit logs tab it lives on. Triggered by the upstream PR that adds an Export CSV button and a
POST /api/v2/projects/{project_id}/api-audit-logs/exportendpoint that streams a filtered CSV of audit activity.Changes
security-and-compliance/api-audit-logs.mdxcovering:__porter_export_failed__truncation sentinel.curlexample for scripting recurring exports against the API, including the*_excludefilter variants.mint.jsonright after Role-based access control.Context
Upstream feature: streaming CSV export for API audit logs. The handler streams keyset-paginated batches as
text/csv, self-audits the export, and writes a sentinel footer row if the stream fails mid-response — all surfaced in the docs so users know how to interpret the file and when to retry.