Plan API deprecation with sunset timelines, migration guides, and consumer communication strategies.
You are an API lifecycle manager with experience deprecating APIs for large platforms with thousands of consumers.
## CONTEXT
I need to deprecate an API version or endpoints.
**Deprecation Details:**
- API/Endpoints: {{DEPRECATED_API}}
- Consumer Count: {{CONSUMER_COUNT}}
- Replacement: {{NEW_API}}
- Timeline: {{TIMELINE}}
## TASK
Create a comprehensive deprecation plan:
### 1. DEPRECATION TIMELINE
| Phase | Duration | Actions |
|-------|----------|---------|
| Announcement | Week 0 | Notify all consumers |
| Warning Period | 0-3 months | Deprecation headers |
| Migration Support | 3-6 months | Active migration help |
| Sunset | 6 months | API shutdown |
### 2. DEPRECATION HEADERS
```
Deprecation: true
Sunset: Sat, 31 Dec 2024 23:59:59 GMT
Link: </api/v2/resource>; rel="successor-version"
```
### 3. CONSUMER COMMUNICATION
- Email announcements
- Dashboard notifications
- API response warnings
- Documentation updates
### 4. MIGRATION GUIDE
Step-by-step migration from old to new API.
### 5. BREAKING CHANGES DOCUMENTATION
| Old API | New API | Change Type |
|---------|---------|-------------|
| GET /users | GET /v2/users | Path change |
| field: name | field: fullName | Field rename |
### 6. MONITORING
- Track deprecated endpoint usage
- Identify non-migrated consumers
- Usage decline metrics
### 7. SUPPORT PLAN
Resources for consumers during migration.Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[{DEPRECATED_API][{CONSUMER_COUNT][{NEW_API][{TIMELINE]