Skip to content
You're offline
Pages won't load until you're back. Anything you send will wait.
We can't reach fam.
Your connection looks fine from here, so this is likely on our side.
Log in
API referencev1

Getting started

The fam. API

Every published endpoint, as it is: the same table the application runs on, described. One base URL, one envelope, one kind of id, a key that acts as its owner: a person, or an integration.

Base URL
https://app.fam.services/api/v1
Auth
Bearer key
Format
JSON · OpenAPI 3.1.0
Endpoints
41 in 12 resources

Three steps

  1. An admin mints a key on the organization's console, Console › API: their own, or an integration's. It is shown once. The key acts as its owner, with the owner's permission profile at every location, and only within its scopes (whose key, which scopes).
  2. Send it as a bearer on every request: Authorization: Bearer fam_…. No cookie, no CSRF token.
  3. Every reply says ok first. A refusal is a 4xx that names its error, the param it is about, a message and its doc_url (the envelope, every word). An id says what it is: ticket_…, user_…. Every reply carries Request-Id; a write takes Idempotency-Key; a list pages on cursor; what happens reaches your webhooks.

Resources

Free 30-minute tour

Pick a time that suits you.

A 30-minute walkthrough with a real person. Times shown in your timezone, .

1 · The day

Select language