feat: Add user API key methods - #1655
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Original prompt from drew.emery
|
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Greptile SummaryThis PR adds
Confidence Score: 5/5Safe to merge — the new methods are additive, well-tested, and follow the SDK's established serialization and pagination patterns exactly. All serializers, deserializers, and interfaces are consistent with existing SDK patterns. Tests cover the full round-trip for both methods including edge cases like idempotency keys and pagination filters. No regressions to existing code paths are possible since both methods are purely additive. No files require special attention. Important Files Changed
|
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Add
userManagement.listUserApiKeys()anduserManagement.createUserApiKey()for the user-scoped API key endpoints. The new types and serializers cover pagination, organization filtering, optional permissions and expiration, idempotency keys, and camel-cased user ownership metadata.This complements #1650, which already added dual-owner
ApiKey.ownertypes and camelizedowner.organizationIdduring validation deserialization.Documentation
Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.
If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.
Link to Devin session: https://app.devin.ai/sessions/d37c887495594308a34bd8db9556dee9
Requested by: @ethinallen