Browse topics
On this page
API Reference
Platform APIs available to custom resources.
API Reference
Custom resources access platform capabilities through typed APIs. Each API requires a capability declared in your resource.json manifest.
Available APIs
| API | Capability | Description |
|---|---|---|
| HTTP | network:http | Outbound HTTP requests (GET, POST, PUT, DELETE, PATCH) with streaming support |
| Storage | storage:kv | Key-value storage scoped to your resource |
Coming Soon
| API | Capability | Description |
|---|---|---|
| Filesystem | fs:resource | Read/write files in a resource-scoped directory |
| Database | database:resource | Per-resource SQLite database |
| WebSocket | network:ws | Persistent connections to external services |
| Credentials | credentials:store | Secure storage for API keys and secrets |
| Hooks | hooks:provide, hooks:consume | Inter-resource communication |
| Relay | relay:channel | Real-time cross-device messaging |
Access Model
All APIs are available from both the frontend (iframe) and the optional backend (Node.js). The underlying implementation is the same — requests route through the Tauri native layer.
Frontend (iframe) → postMessage → Bridge → Tauri Command → Result
Backend (Node.js) → JSON-RPC → Handler → Tauri Command → Result