Stair headroom calculator
Straight-flight design fails when the nosing line under the upper-floor soffit leaves less vertical clearance than your building code allows.
Run — free
This stair headroom calculator turns finished floor-to-floor height, stair pitch angle and the horizontal length of the stairwell opening into available headroom at the critical edge, then compares that figure with a code minimum you choose—or with the common two-thousand-thirty-two unit default that matches six feet eight inches when you work in millimetres. Optional slab thickness subtracts structure depth so the clearance is measured to the underside of the floor, not to the finished surface above. The same pure arithmetic powers the free browser widget and the prepaid API, so takeoff tools, renovation apps and site checks never disagree on whether a proposed opening is long enough. Failed validation is not billed; successful item calls use the published $0.002 base price on KIT balance.
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
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/home/stair-headroom \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"floor_to_floor_height":2800,"stair_angle":32,"floor_opening_length":3200}'const res = await fetch("https://api.kit.forhosting.com/home/stair-headroom", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"floor_to_floor_height": 2800,
"stair_angle": 32,
"floor_opening_length": 3200
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/home/stair-headroom",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"floor_to_floor_height": 2800,
"stair_angle": 32,
"floor_opening_length": 3200
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/home/stair-headroom", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"floor_to_floor_height":2800,"stair_angle":32,"floor_opening_length":3200}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"floor_to_floor_height":2800,"stair_angle":32,"floor_opening_length":3200}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/home/stair-headroom", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"floor_to_floor_height": 2800,
"stair_angle": 32,
"floor_opening_length": 3200
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "home.stair_headroom",
"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
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. |