The Challenge
API documentation constantly falls out of sync with code. Engineers add endpoints without updating docs, and maintaining accurate examples requires ongoing effort.
The AI Desk Solution
AI Desk monitors code changes and generates documentation updates, keeping docs in sync with implementation.
The Workflow
Step 1: Code Change Detection
Trigger: PR merged with API changes
Sources: Code diff, OpenAPI spec, existing docs
Step 2: Documentation Analysis
- Identify new/changed endpoints
- Generate descriptions
- Create examples
- Update changelog
Step 3: Doc Updates
š API Documentation Update
PR: feat/user-preferences (#4521)
NEW ENDPOINTS DOCUMENTED
GET /api/v2/users/{id}/preferences
āāā Description: Retrieve user preferences
āāā Auth: Bearer token required
āāā Parameters:
ā āāā id (path): User ID
āāā Response: 200 OK
ā {
ā "theme": "dark",
ā "notifications": true,
ā "timezone": "America/New_York"
ā }
āāā Example added ā
PUT /api/v2/users/{id}/preferences
āāā Description: Update user preferences
āāā Auth: Bearer token required
āāā Body: Partial preference object
āāā Response: 200 OK (updated preferences)
āāā Example added ā
CHANGELOG ENTRY
v2.4.0 - User Preferences API
āāā Added GET /users/{id}/preferences
āāā Added PUT /users/{id}/preferences
āāā Breaking: None
ACTIONS
āāā [Review documentation PR]
āāā [Publish to developer portal]
āāā [Notify API subscribers]
Value Proposition
- Time Saved: 2 hours per API change
- Always Current: Auto-sync with code
- Consistent Format: Standard structure
Part of the 100 Days 100 Usecases campaign. View all usecases