Update Cove TODO: API exists but activation method unknown

Added critical information from user:
- Confirmed: Cove Data Protection HAS API access (documented)
- Problem: Location/method to enable API access is unknown

Changes:
- Added Phase 0: API Access Activation (critical first step)
- Marked API availability as confirmed
- Added checklist for finding API activation in admin portal
- Listed possible admin portal locations to check
- Added support channel suggestions if activation unclear
- Updated current status section with latest info

Next action: Investigate Cove admin portal or contact support for
API activation instructions.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

TODO-cove-data-protection.md

@@ -17,11 +17,13 @@ Integrate Cove Data Protection (formerly N-able Backup / SolarWinds Backup) into
 ## 🔍 Research Questions
 
 ### 1. API Availability
-- [ ] Does Cove Data Protection have a public API?
+- [x] Does Cove Data Protection have a public API? **YES - Confirmed in documentation**
+- [ ] **CRITICAL:** How to enable/activate API access? (settings location, admin portal?)
 - [ ] What authentication method does the API use? (API key, OAuth, basic auth?)
 - [ ] Which endpoints are available for backup status?
 - [ ] Is there rate limiting on the API?
 - [ ] Documentation URL: ?
+- [ ] Is API access available in all Cove subscription tiers or only specific plans?
 
 ### 2. Data Structure
 - [ ] What information can we retrieve per backup job?
@@ -101,6 +103,42 @@ Unified  →                → Common Processor → JobRun
 
 ## 🔧 Implementation Steps (After Research)
 
+### Phase 0: API Access Activation (FIRST!)
+**Critical step before any development can begin:**
+
+1. [ ] **Find API activation location**
+   - Check Cove admin portal/dashboard
+   - Look in: Settings → API / Integrations / Developer section
+   - Check: Account settings, Company settings, Partner settings
+   - Search documentation for: "API activation", "API access", "enable API"
+
+2. [ ] **Generate API credentials**
+   - API key generation
+   - Client ID / Client Secret (if OAuth)
+   - Note: which user/role can generate API keys?
+
+3. [ ] **Document API base URL**
+   - Production API endpoint
+   - Sandbox/test environment (if available)
+   - Regional endpoints (EU vs US?)
+
+4. [ ] **Document API authentication flow**
+   - Header format (Bearer token, API key in header, query param?)
+   - Token expiration and refresh
+   - Rate limit headers to watch
+
+5. [ ] **Find API documentation portal**
+   - Developer documentation URL
+   - Interactive API explorer (Swagger/OpenAPI?)
+   - Code examples/SDKs
+   - Support channels for API questions
+
+**Resources to check:**
+- Cove admin portal: https://backup.management (or similar)
+- N-able partner portal
+- Cove knowledge base / support docs
+- Contact Cove support for API access instructions
+
 ### Phase 1: API Research & POC
 1. [ ] Research Cove API documentation
 2. [ ] Test API authentication
@@ -202,3 +240,24 @@ Other backup systems that use APIs:
 - Add API examples as soon as available
 - Document edge cases and limitations
 - Consider security implications (API key storage, rate limits, etc.)
+
+### Current Status (2026-02-10)
+- ✅ **Confirmed:** Cove Data Protection HAS API access (mentioned in documentation)
+- ❓ **Unknown:** How to enable/activate API access in Cove portal
+- ❓ **Unknown:** API documentation location
+- 🎯 **Next action:** Find API activation instructions in Cove admin portal or contact support
+
+### Possible Admin Portal Locations
+Check these sections in Cove dashboard:
+- Settings → API Keys / Developer
+- Settings → Integrations
+- Account → API Access
+- Partner Portal → API Management
+- Company Settings → Advanced → API
+
+### Support Channels
+If API activation is not obvious:
+- Cove support ticket: Ask "How do I enable API access for backup monitoring?"
+- N-able partner support (if MSP)
+- Check Cove community forums
+- Review onboarding documentation for API mentions