Elian Book API

Overview Read-only

Every endpoint is a GET under a single base URL. Responses are JSON. A key can read only the workspace it was created in, and can only read - there is no write, update, or delete surface. If you need to get data out of Elian Book and into another tool, this is the API for it.

Authentication

Create a key in the app under Settings → API access. Only a workspace owner or admin can mint one. The raw key is shown once at creation - copy it then and store it somewhere secure; Elian Book keeps only a hash and can never show it again.

Send it on every request as a bearer token:

# every request carries the key in the Authorization header
curl https://elianbook.com/api/v1/transactions \
  -H "Authorization: Bearer eb_live_your_key_here"

Pagination

List endpoints return a page of rows plus the page window, and accept limit and offset query params. Default page size is 100; the maximum is 500. Walk the pages by increasing offset until a page returns fewer rows than the limit.

GET /api/v1/transactions?limit=500&offset=1000

{
  "data": [ /* up to `limit` rows */ ],
  "limit": 500,
  "offset": 1000
}

The report and export endpoints are not paginated - they return a single object.

Errors

Errors come back as JSON with an error message and a matching HTTP status.

Quickstart

A complete example - "which projects did a given employee work on" - joined entirely client-side from the data the API serves:

const H = { Authorization: 'Bearer eb_live_your_key_here' };

// walk every page of a list endpoint
async function all(path) {
  const out = [];
  for (let offset = 0; ; offset += 500) {
    const r = await fetch(`https://elianbook.com/api/v1${path}?limit=500&offset=${offset}`, { headers: H });
    const { data } = await r.json();
    out.push(...data);
    if (data.length < 500) break;
  }
  return out;
}

const logs = await all('/time-logs');
const projectIds = new Set(logs.filter(l => l.employee_id === EMPLOYEE_ID).map(l => l.project_id));
const projects = (await all('/projects')).filter(p => projectIds.has(p.id));

Because every record carries the ids that link it to others (employee_id, project_id, client_id, invoice_id, category_id, account_id), you can reconstruct any relationship in your own code.