docs: clarify CSV export download token expiry and auth headers#1282
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: clarify CSV export download token expiry and auth headers#1282mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
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
Clarify that the CSV export download URL requires authentication headers in addition to its embedded
token, and that the token is short-lived — a recurring source of401 Unauthorizedconfusion.Changes
guides/csv-export.mdx: added a callout under the download step covering region-specific base URLs, the requirement to sendX-App-Id/X-App-Tokenalongside thetokenquery parameter, and the short-lived nature of the token (re-fetch via Get Export if401).openapi/exports.json: mirrored the same notes into the Download Export endpoint description so readers hitting the API reference see them too.Context
Assistant signal showed multiple threads where users obtained a valid
result.urlfrom Get Export but then hit401 Unauthorizedon download — either because they sent only thetokenwithout auth headers, or because the token expired between Get Export and download. The existing guide mentioned "use the provided URL together with authentication headers" without explaining either pitfall.