API overview

Integrate with Felagar using the /v1 REST API, API keys, or OAuth.

The public API is the same /v1 REST surface agencies use internally, authenticated with:

Agency API keys (fel_…) for server-to-server automation
OAuth apps for interactive client products
Session cookies for first-party dashboard use

Base URL (hosted): https://api.felagar.app
Self-host: your public API origin (local http://localhost:3041)

Quick check

curl https://api.felagar.app/v1/health

const res = await fetch('https://api.felagar.app/v1/health')
const json = await res.json()
console.log(json)

import requests
print(requests.get('https://api.felagar.app/v1/health').json())

Replace the API host with your self-hosted URL when applicable.

Typical client integration

Agency creates an API key or OAuth app in Settings → API keys
Client backend stores the key/secret
Client calls Felagar to read projects, push tickets, sync files, or receive outbound webhooks

Scopes

API keys can be limited to: projects, tickets, files, designs, companies, pipeline, time-entries, chat, migration, team.

MCP OAuth clients typically use tool scopes such as tickets, projects, designs, and time (enforced at tool call time, with an agent action audit in Settings → MCP).

Reference

The machine-readable contract ships as openapi/v1.yaml in the monorepo. Use it to generate clients or import into Postman.