ForHosting KIT · Developer Utilities

FTE headcount calculator

Headcount alone hides how much labor you actually buy when part-time, reduced-hours, and full-time people sit on the same roster.

● BetaFree · in your browser

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

Finance and HR teams need a single full-time-equivalent number that weights each person by scheduled weekly hours against a standard full-time week—commonly forty hours, sometimes thirty-five or thirty-seven and a half depending on region and policy. This FTE headcount calculator accepts every staff row with weekly hours, divides each by your standard full-time week, and sums the fractions so budget models, org charts, and headcount reports speak the same language. Controllers use it when a mix of twenty-hour and forty-hour roles must become one FTE line. Operations leads use it before approving another hire against an FTE cap. Planning scripts use the same pure arithmetic so the free browser widget and the API never disagree on a total that should be reproducible across payroll exports and board decks.

How to use it

Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.

Check your inputs

Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.

Use it again or automate it

Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.

What you can do with it

Get an answer now

Enter one set of values and see the result without building a spreadsheet or script.

Compare scenarios

Change one value at a time and rerun the calculation to understand what affects the result.

Automate repeated work

Use the API when the same calculation needs to run inside your product or workflow.

FAQ

How do I use this capability?

Complete the fields above and run it on this page. The form highlights anything that needs attention.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/biz/fte-headcount

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/biz/fte-headcount \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"staff":[{"name":"Ana","weekly_hours":40},{"name":"Ben","weekly_hours":20},{"name":"Cara","weekly_hours":30}]}'

const res = await fetch("https://api.kit.forhosting.com/biz/fte-headcount", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "staff": [
      {
        "name": "Ana",
        "weekly_hours": 40
      },
      {
        "name": "Ben",
        "weekly_hours": 20
      },
      {
        "name": "Cara",
        "weekly_hours": 30
      }
    ]
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/biz/fte-headcount",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "staff": [
        {
            "name": "Ana",
            "weekly_hours": 40
        },
        {
            "name": "Ben",
            "weekly_hours": 20
        },
        {
            "name": "Cara",
            "weekly_hours": 30
        }
    ]
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/biz/fte-headcount", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"staff":[{"name":"Ana","weekly_hours":40},{"name":"Ben","weekly_hours":20},{"name":"Cara","weekly_hours":30}]}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"staff":[{"name":"Ana","weekly_hours":40},{"name":"Ben","weekly_hours":20},{"name":"Cara","weekly_hours":30}]}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/biz/fte-headcount", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "staff": [
    {
      "name": "Ana",
      "weekly_hours": 40
    },
    {
      "name": "Ben",
      "weekly_hours": 20
    },
    {
      "name": "Cara",
      "weekly_hours": 30
    }
  ]
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "biz.fte_headcount",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.

Read the full KIT documentation →