Compatibility

Cloud and desktop compatibility

Capability	Cloud	Desktop
Base URL	https://api.alshival.ai	http://127.0.0.1:8765 when enabled
Credentials	Portal-managed cloud credentials	Locally issued scoped tokens
JSON resource logs	Workspace/resource /logs	Same path and payload contract
OTLP resource logs	Workspace/resource /otlp/v1/logs	Same HTTP JSON/protobuf contract
Log query cursors	Cloud destination only	Local destination only
Project routes	Workspace task/board/note routes	/v1/projects/items and catalogs
Retention	Cloud workspace policy	Device settings and disk quotas
Owner settings	Portal permissions	Private Unix socket/desktop IPC

Switch a logging destination

Change the base URL and credential together. Retain workspace/resource IDs only when they identify the same synced resource at both destinations. A local-only resource must first exist at the cloud destination; copying its local UUID into a cloud URL does not create it.

Start a fresh query after switching; cursors are not portable. Historical logs do not migrate automatically. Enabling workspace sync does not enable cloud forwarding.

Legacy logging

The older desktop /v1/logs route uses a different batch limit, severity vocabulary, caller-supplied event IDs, and response format. It remains for existing clients. New integrations should use workspace/resource routes.

Older DevTools Resource URL, X-API-Key, logs/level/extra, and ALERT examples are not the new workspace API contract. Do not mix those fields or headers into the examples in this guide.

---

Published from the versioned Alshival documentation source. Edit the source rather than this generated page.