Greptile Overview

Greptile Summary

Added new apiKeys.validateApiKey method to the SDK that exposes WorkOS's API key validation endpoint. The implementation follows established patterns in the codebase.

• New ApiKeys class with validateApiKey method that sends POST requests to /api_keys/validations
• Proper serialization/deserialization for snake_case API responses to camelCase SDK format
• Handles both valid API key responses and null (invalid) responses correctly
• Comprehensive test coverage for valid and invalid key scenarios
• No security issues detected - API key values are only sent in the request payload, not logged
• Consistent with existing SDK patterns for error handling and type definitions

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• Clean implementation following established SDK patterns with comprehensive test coverage and no security concerns
• No files require special attention

Important Files Changed

File Analysis

Sequence Diagram

sequenceDiagram
    participant App as Developer Application
    participant SDK as WorkOS SDK
    participant API as WorkOS API
    
    App->>SDK: workos.apiKeys.validateApiKey({ value })
    SDK->>SDK: Serialize request payload
    SDK->>API: POST /api_keys/validations
    Note over SDK,API: Payload: { value: "sk_..." }
    API->>API: Validate API key
    alt Valid API Key
        API-->>SDK: { api_key: { id, owner, permissions, ... } }
        SDK->>SDK: Deserialize response
        SDK-->>App: { apiKey: ApiKey }
    else Invalid API Key
        API-->>SDK: { api_key: null }
        SDK->>SDK: Deserialize response
        SDK-->>App: { apiKey: null }
    end

_{8 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}