Open
Conversation
Generated-By: mintlify-agent
mintlify
bot
requested review from
Flo4604,
MichaelUnkey,
chronark,
imeyer,
mcstepp,
ogzhanolguncu and
perkinsjr
as code owners
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
Adds documentation for the
lastUsedAtfield, a new API response field that tracks when each key was last used for verification. This was shipped in the week of March 17-23 and referenced in the changelog, but lacked dedicated documentation on the API keys page.Changes
lastUsedAtfield, which endpoints return it, its precision, and a TypeScript code examplelastUsedAtis not part of thekeys.verifyKeyresponse/apis/features/analytics) to point to/analytics/overviewapis/features/analyticsnav entry from docs.json (a redirect already exists)Triggered by unkeyed/unkey#5437, which corrected the
lastUsedAtfield name and endpoint references in the changelog.