The Folke API

The Folke API lets another tool read from Folke: a payroll system that needs everyone’s leave, a spreadsheet of who’s off this week, a dashboard on the office screen. It only reads. Nothing sent to it can book, approve or change anything.

Pro plan

The API is part of the Pro plan, and only organisation admins can create keys.

What you can read

Endpoint	What it gives you
GET /org/people	Everyone in your organisation
GET /org/leave	Leave in a date range, approved by default
GET /org/whos-off	Who’s off on a given day
GET /org/leave-types	The leave types your organisation offers
GET /org/bank-holidays	The bank holidays your organisation observes

Every address starts with:

https://api.myfolke.com/api/v1

Your first request

1. In Folke, go to Organisation Settings > API and choose Create key. Give it a name you’ll recognise, like the tool it’s for.
2. Copy the key. It’s shown once.
3. Send it with a request:

curl https://api.myfolke.com/api/v1/org/whos-off \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Accept: application/json"

You get back today’s approved leave:

{
  "data": [
    {
      "id": 4182,
      "person": { "id": 12, "name": "Priya Shah", "email": "priya@example.com" },
      "type": { "id": 1, "name": "Annual Leave" },
      "startDate": "2026-10-26",
      "endDate": "2026-10-30",
      "startsAfternoon": false,
      "endsMorning": false,
      "startTime": null,
      "endTime": null,
      "days": 5,
      "status": "approved",
      "closure": false,
      "requestedAt": "2026-09-14T10:26:00+01:00",
      "decidedAt": "2026-09-14T15:02:00+01:00"
    }
  ],
  "meta": { "date": "2026-10-26" }
}

Good to know

• It reads your whole organisation. A key acts as the admin who made it, and admins see everyone.
• What stays private. It never includes dates of birth, photos or the notes team members write on their leave requests, which are often about being unwell.
• Answers are JSON, with what you asked for in data and anything about it, like the page you’re on, in meta.
• Dates are YYYY-MM-DD and times are ISO 8601 with their offset.
• We only add, never take away. New fields may appear in a response, so read the ones you need and ignore the rest. A field you rely on won’t be renamed or removed.

Next: keys and authentication.