hootsuite-reference-architecture

# Hootsuite Reference Architecture ## Architecture ``` ┌──────────────────────────────────────┐ │ Your Application │ ├──────────────────────────────────────┤ │ Content Manager → Scheduler → Publisher │ ├──────────────────────────────────────┤ │ Hootsuite API Client │ │ (OAuth, Token Refresh, Rate Limit) │ ├──────────────────────────────────────┤ │ Hootsuite REST API v1 │ │ platform.hootsuite.com/v1/ │ └──────────────────────────────────────┘ ``` ## Project Structure ``` hootsuite-integration/ ├── src/ │ ├── hootsuite/ │ │ ├── client.ts # API client with token management │ │ ├── auth.ts # OAuth 2.0 flow │ │ ├── publishing.ts # Message scheduling + media │ │ ├── analytics.ts # Metrics + URL shortening │ │ └── types.ts # TypeScript interfaces │ ├── services/ │ │ ├── scheduler.ts # Content calendar logic │ │ ├── content.ts # Post formatting per platform │ │ └── media.ts # Media processing + upload │ ├── api/ │ │ └── schedule.ts # REST endpoint │ └── store/ │ └── tokens.ts # Persistent token storage ├── tests/ │ ├── unit/ │ └── fixtures/ └── .env.example ``` ## Key Decisions | Decision | Recommendation | Why | |----------|---------------|-----| | Token storage | Database/KV, not env vars | Refresh tokens change each use | | Scheduling | Queue-based, not direct API | Rate limit compliance | | Me...