The public product material reviewed for this repository describes API-based login and management at a high level, but does not publish a complete public endpoint specification. This document is therefore a Reference Architecture, not an API contract for a live service.
| Resource | Purpose |
|---|---|
| Account | Identity, profile mapping, permissions, health state |
| Task | A single observable action with an idempotency key |
| Schedule | Time window, timezone, recurrence, and jitter policy |
| Event | Progress, review, success, or failure record |
| Analytics | Aggregated delivery and engagement measurements |
sequenceDiagram
participant App as Client
participant API as Integration boundary
participant Q as Task queue
participant W as Worker
participant Log as Event store
App->>API: Submit reviewed task
API->>Q: Validate and enqueue
Q->>W: Lease task
W->>Log: Emit started event
W->>Log: Emit result or review-needed event
API-->>App: Return task status
Possible integration surfaces include account management, task submission, scheduling, analytics, and webhooks. Endpoint names, authentication schemes, payloads, and quotas must be defined against the actual provider or deployment before implementation.