Obsidian · Rate Limits

Obsidian Rate Limits

Obsidian itself does not publish a hosted SaaS API and therefore has no remote rate-limit ceilings. The Plugin API runs in-process and is bounded only by the host device. The community Local REST API plugin runs on localhost and has no published rate-limit policy beyond the device's own throughput. Sync and Publish are managed add-ons whose throughput is bounded by the device and Obsidian-operated infrastructure.

Obsidian Rate Limits is the machine-readable rate-limit profile for Obsidian on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring none and not published.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Productivity, Knowledge Management, Markdown, Notes, and Local-First.

4 Limits Throttle: 429
ProductivityKnowledge ManagementMarkdownNotesLocal-FirstRate LimitingQuotasThrottling

Limits

Plugin API (In-Process) device
none
-1
No platform-imposed rate limit; bounded by local CPU and event loop.
Local REST API Plugin device
none
-1
No published rate limit; bounded by local Obsidian process. Recommend client-side concurrency caps.
Obsidian Sync (Add-On) account
not published
not published
Sync is a closed managed service with no publicly documented rate-limit policy.
Obsidian Publish (Add-On) site
not published
not published
Publish is a closed managed service with no publicly documented rate-limit policy.

Policies

Local Concurrency
When automating against the Local REST API plugin, cap concurrent requests to keep the local Obsidian UI responsive.
Self-Signed TLS
The Local REST API uses self-signed HTTPS certificates; clients must trust the certificate or use the API key over HTTP if enabled.

Sources