Skip to main content
Each desktop app (Post, Flock, Loft, Migrate) starts a local Bridge — an ASP.NET Core sidecar — on a fixed port while it’s running. The desktop apps themselves use this same API. There is no public hosted API today: every request in this reference is local to the machine running the app, on a loopback port reachable only while that app is open. Base URL: http://localhost:<port>, where the port depends on which app’s Bridge you’re calling: The endpoints below (Loft interfaces/alerts/status/analytics/traces, Flock, Admin, Enterprise) are Loft- and Flock-scoped and default to their Bridge’s port in the examples that follow; substitute the port for the app you’re integrating with.
This reference documents the local Bridge HTTP contract for automation and integration against a running desktop app. It has not been exhaustively cross-checked against every current Bridge route — if an example here 404s, prefer the CLI equivalent and treat the mismatch as a docs bug.

​
Authentication

Two authentication schemes are supported. Include one on protected endpoints:

​
Response Format

​
Authorization Policies

​
Usage limits

Because the Bridge runs locally, there’s no network-abuse rate limit to enforce — usage limits instead follow your account’s plan and entitlements (for example, Flock’s population size caps in the desktop app’s Population panel). Where a response includes rate-limit headers, they reflect the entitlement-based cap for that endpoint, not a fixed per-tier number documented here.

​
Endpoint Groups

​
Content Type

All request and response bodies use JSON. Set Content-Type: application/json on all requests with a body.