📄️ Core APIs
The Qirvo Plugin SDK provides a comprehensive set of APIs for interacting with the Qirvo platform. This reference covers all core APIs available to plugin developers.
📄️ Plugin Context
The Plugin Context provides the runtime environment and services available to your plugin during execution. This guide covers the complete context interface and how to use it effectively.
📄️ Base Plugin Class
This document describes the canonical Base Plugin Class used by Qirvo hosts. It contains the TypeScript contract, lifecycle behavior, examples, error modes, and best practices for plugin implementers.
📄️ Storage API
The Storage API provides persistent, secure key-value storage for your plugins. This guide covers all storage capabilities, patterns, and best practices.
📄️ HTTP Client API
The HTTP Client API provides secure, permission-controlled access to external APIs and web services. This guide covers all HTTP capabilities, patterns, and best practices.
📄️ Notification API
The Notification API provides a typed mechanism for plugins and host components to send user-facing and system notifications. It supports immediate notifications, scheduled/delayed notifications, and multiple channels (in-app, email, webhook) depending on host capabilities.
📄️ Event System
The Event System enables real-time communication between plugins, the Qirvo platform, and external systems. This guide covers event handling, custom events, and communication patterns.
📄️ Logger API
The Logger API provides a simple, structured logging interface for plugins and host components. It supports leveled logs, named loggers, and optional structured metadata.
📄️ Configuration API
The Configuration API exposes a typed key-value store that plugins can use to read and update runtime configuration. Hosts may persist configuration to disk, a database, or a remote config service.
📄️ Qirvo Integration APIs
The Qirvo Integration APIs provide direct access to Qirvo's core platform features including tasks, calendar, journal, and user data. This guide covers all available integrations and usage patterns.