Skip to main content
The Friday daemon is the local backend service that runs spaces, orchestrates agents, manages sessions, and exposes an HTTP API for programmatic access. Everything you can do in Friday Studio — and more — is reachable through this API.

​
How it runs

The daemon ships with Friday Studio and starts automatically when you launch the app. The installed app serves the API at https://local.hellofriday.ai:18080 — a loopback hostname that resolves to your machine, with a trusted TLS certificate so the browser and curl accept it without warnings. Because the daemon binds to your local machine, no authentication is required and traffic never leaves it — your spaces, prompts, and outputs stay local. Studio is a web UI that talks to this same API. The CLI and SDK do too. That means anything you build against the API — scripts, automations, integrations — works the same way Studio does, against the same surface.

​
Endpoint groups

The daemon organizes endpoints into a small set of resource groups. Each group has its own reference page with request and response schemas:
GroupWhat it does
HealthDaemon liveness and status — verify the daemon is reachable
SpacesCreate, list, register, configure, and delete spaces
ChatSend a prompt to a space and stream the response
SessionsInspect running and historical job sessions
SignalsTrigger automations from your own code
AgentsDiscover the agents available to a space
ArtifactsRetrieve files, reports, and data produced by agents
ConfigurationRead and update daemon environment variables

​
Health check

Use the health endpoint to confirm the daemon is up before issuing other requests: 
curl https://local.hellofriday.ai:18080/health
A running daemon responds with a JSON object describing how many spaces are loaded, how long it’s been up, and the runtime it’s built on: 
{
  "activeWorkspaces": 3,
  "uptime": 3600000,
  "timestamp": "2026-03-24T10:00:00.000Z",
  "version": { "deno": "...", "v8": "...", "typescript": "..." }
}
If the call fails, Friday Studio isn’t running — launch it and retry.

​
Streaming responses

Chat and session endpoints support Server-Sent Events (SSE) so you can stream model output as it’s generated. Add -N to curl (or set Accept: text/event-stream from your HTTP client) to keep the connection open and receive events as they arrive: 
curl -N -X POST https://local.hellofriday.ai:18080/api/workspaces/{workspaceId}/chat \
  -H 'Content-Type: application/json' \
  -d '{
    "id": "chat-001",
    "message": { "role": "user", "content": "What can you help me with?" }
  }'
The same pattern works for any endpoint that emits incremental progress — including signal triggers that you want to follow in real time via a streamId.

​
Webhook tunnel

To receive webhooks from external services like GitHub, Bitbucket, or Jira, the platform includes a webhook tunnel on port 19090 that exposes a public URL through Cloudflare. The tunnel forwards inbound requests to your local daemon, so HTTP signals work even when Friday is only running on your laptop. See HTTP signals for tunnel setup, payload examples, and security guidance.

​
Triggering signals from your code

Signals are the canonical way to start jobs. Once a signal is defined in your workspace.yml, you can fire it from anywhere — a cron, another agent, a button in your own UI — by POSTing to its endpoint: 
curl -X POST https://local.hellofriday.ai:18080/api/workspaces/{workspaceId}/signals/{signalId} \
  -H 'Content-Type: application/json' \
  -d '{ "payload": { "key": "value" } }'
The payload is passed through to the job. See Signals for the conceptual model and Triggering signals manually for CLI and Studio equivalents.

​
When to use the API

  • Build a custom integration — embed Friday into your own product, dashboard, or workflow tool.
  • Automate from CI or scripts — kick off jobs from GitHub Actions, scheduled tasks, or your shell.
  • Pipe outputs to other systems — fetch artifacts and forward them to storage, chat, or downstream pipelines.
  • Drive multiple spaces — manage many spaces from a single script instead of the Studio UI.
For day-to-day usage, Studio and the CLI wrap these endpoints — reach for the API when you need to script, integrate, or automate.

​
API reference

For the full list of endpoints with request and response schemas, parameter details, and an in-browser Try it panel, see the API reference.