feat(api-keys): add last_used_at field to API key response#877
Merged
joaopcm merged 1 commit intoMar 13, 2026
Merged
Conversation
Support nullable last_used_at timestamp for API keys in list response, matching API spec.
last_used_at field to API key response
commit: |
Contributor
There was a problem hiding this comment.
cubic analysis
No issues found across 3 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Linked issue analysis
Linked issue: PRODUCT-1583: Coordinate last_used_at change
| Status | Acceptance criteria | Notes |
|---|---|---|
| ❌ | Update the docs to talk about the new field | No docs updated in diffs |
| ❌ | OpenAPI spec | No OpenAPI/spec files changed |
| ❌ | Update the Node.js SDK to support this new field | No SDK code or package changes present |
| ❌ | Coordinate with SDK maintainers | No coordination notes or related changes |
| ❌ | Let the Chrisis know | No notification or changelog updates found |
| ✅ | Add last_used_at field to API response types and tests (repository) | Added interface, response type, and test fixtures |
| ✅ | Ensure last_used_at is nullable and ISO-8601 when present | Type allows string|null and tests show ISO-8601 sample |
gabrielmfern
approved these changes
Mar 12, 2026
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
2 participants
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
Added support for the nullable
last_used_atfield in the API keys list response. The field returns an ISO-8601 timestamp string when available, or null if never used. Updated theApiKeyinterface, response types, and test fixtures to reflect the API spec change.Testing steps
apiKeys.list()returns objects withlast_used_atfieldlast_used_atcan be null or contain an ISO-8601 timestamppnpm testto ensure all tests passpnpm lint:fixto verify no linting issuesSummary by cubic
Add a nullable
last_used_attimestamp to API key list responses so clients can see when each key was last used. UpdatesApiKeytypes to match the API spec and satisfy PRODUCT-1583.ApiKeywithlast_used_at: string | nulllast_used_atinapiKeys.list()results (ISO-8601 string or null)Written for commit deb9118. Summary will update on new commits.