🔑 API & Integrations

Inspect backend platform auth, optionally use a tab-local key for direct API tests, and review ecosystem integrations.

Platform Auth

Calendar uses the shared PLATPHORM_API_KEY only. Backend operators configure it server-side; this tab-local field is only for direct protected API testing and is never stored in localStorage or IndexedDB.

Service-specific Calendar keys are disabled. Protected event persistence, integration sync, reminder mutation, reporting, and MCP tool execution use the backend platform key or a matching protected request header. The backend status is exposed only as a configured/not-configured boolean at /api/v1/storage/status.

Authentication

How API key authentication works

Public Access (No Key): All public calendar events are accessible without authentication. Perfect for read-only integrations and public calendars.
Authenticated Access (With Key): Include PLATPHORM_API_KEY to access private events, create/update server events, and manage integrations. Use X-PlatPhorm-API-Key or Authorization: Bearer <key>.
Base URL: https://calendar.platphormnews.com/api/v1