Drain field area & trench
API · /septic-api
Septic System API
healthy
4,552 Subscribers
Septic-system sizing as an API, computed locally and deterministically with the typical US onsite-wastewater rules of thumb. The flow endpoint estimates the design wastewater flow for a home from its number of bedrooms (assuming two people per bedroom) or an explicit occupancy, at a default 60 gallons per person per day, returning the daily flow in US gallons and litres. The tank endpoint recommends a septic tank size as the larger of a retention-based size (flow × retention days, default two days) and the typical bedroom-based code minimum (≤3 bedrooms 1,000, 4 bedrooms 1,200, 5 bedrooms 1,500, 6 bedrooms 2,000 US gallons), and tells you which one governs. The drainfield endpoint sizes the soil absorption (leach) field: it divides the daily flow by a soil loading rate — given directly or looked up from a percolation rate in minutes per inch — to get the absorption area, then divides by the trench width to get the trench length, in both imperial and metric. Everything is computed locally and deterministically, so it is instant and private. An estimating aid, not a code-stamped design — always confirm with your local health authority. Ideal for plumbing and septic-installer tools, rural real-estate and land apps, home-building and permitting calculators, and inspection software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is septic / onsite-wastewater sizing; for storage-tank volume and fill level use a tank API.
api.oanor.com/septic-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 87 ms
- Server probes · 24h
- Subscribers
- 4,552
- active
- Total calls
- 40
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 13,635 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 13,635 calls/month
- 2 req/sec
- Flow + tank + drain field
- No credit card
Starter
€15.15 /month
- 23,350 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 23.35k calls/month
- 8 req/sec
- Code minimums, perc loading
- Email support
Pro
€35.25 /month
- 283,500 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 283.5k calls/month
- 20 req/sec
- Plumbing / permitting pipelines
- Priority support
Mega
€73.25 /month
- 1,460,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 1.46M calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Water Hardness API
Water-hardness maths as an API, computed locally and deterministically. The convert endpoint converts a hardness value between all the common units — parts per million / milligrams per litre as calcium carbonate, grains per US gallon, German degrees (°dH), French degrees (°f), English or Clark degrees, and millimoles per litre — passing everything through ppm (1 gpg = 17.118 ppm, 1 °dH = 17.848, 1 °f = 10, 1 °Clark = 14.254), and classifies the result. The classify endpoint labels a value as soft, moderately hard, hard or very hard on the USGS/WHO scale. The softener endpoint sizes a water softener: from the hardness and the household water use it works out the grains of hardness removed per day and the grain capacity needed between regenerations. Everything is computed locally and deterministically, so it is instant and private. Ideal for water-treatment and plumbing tools, aquarium and pool apps, appliance and softener sizing, and home and lab software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is water-hardness conversion; for general unit conversion use a unit-conversion API and for swimming-pool dosing use a pool API.
api.oanor.com/hardness-api
ADA Ramp API
ADA wheelchair-ramp maths as an API, computed locally and deterministically — the run, landing and slope numbers a builder or accessibility planner sizes a ramp by. The rule the ADA fixes is 1 inch of rise per 12 of run, a maximum 8.33 % slope, so the ramp endpoint turns a rise into the ramp: run = rise × 12 (or × 16 / × 20 for a gentler grade if you have the room), plus the level landings the code requires — a 5-foot landing top and bottom and another between runs whenever the rise exceeds 30 inches — and the total length end to end, so a 24-inch rise needs a 24-foot run and 34 feet overall, while a 36-inch rise breaks into two runs with an intermediate landing for 51 feet. The fit endpoint answers the real-world question: does a ramp for this rise fit the run you have? It returns the minimum run an ADA 1:12 ramp needs, whether your space is enough, and the slope you would actually get if you forced it in — flagging when that exceeds 8.33 % and you need a switchback or a lower rise. Everything is computed locally and deterministically, so it is instant and private. Ideal for construction, accessibility, home-modification and contractor app developers, ramp-estimator and code-check tools, and building software. Pure local computation — no key, no third-party service, instant. Confirm against current ADA and local code. Live, nothing stored. 2 compute endpoints.
api.oanor.com/adaramp-api
Deck Builder API
Deck-building maths as an API, computed locally and deterministically — the board, joist and fastener counts a homeowner or contractor needs to material out a rectangular deck. The boards endpoint turns the deck size into a real shopping list: rows = deck width ÷ (board width + gap), rounded up, so a 16 ft × 12 ft deck with a 5.5-inch board face (a 5/4×6) and a 1/8-inch gap needs 26 rows; boards run the length, each row takes one 16 ft board, and a 10 % waste allowance brings it to 29 boards plus the linear footage and the deck area. The joists endpoint frames it: joists are spaced along the length, so count = ⌊length ÷ spacing⌋ + 1 — thirteen joists at 16-inch on-center (seventeen at 12-inch for stronger or diagonal decking), each spanning the width, plus two rim joists and a ledger as total framing linear feet. The fasteners endpoint counts the screws: every decking row crosses every joist once and is fastened with two face screws there, so a 16×12 deck takes 26 × 13 × 2 = 676 screws, about 744 with waste — or one hidden clip per intersection. Everything is computed locally and deterministically, so it is instant and private. Ideal for construction, contractor, home-improvement, building-materials and renovation app developers, deck-estimator and takeoff tools, and lumber-yard calculators. Pure local computation — no key, no third-party service, instant. US units (feet/inches). Live, nothing stored. 3 compute endpoints. Rectangular decks; for indoor floor area use a flooring API.
api.oanor.com/deck-api
Masonry Estimating API
Masonry estimating maths as an API, computed locally and deterministically — the brick, block and mortar counts a bricklayer, builder or estimator works to. The brick endpoint computes how many bricks a wall needs from its area (or length × height in feet): bricks per square foot = 144 / ((brick length + joint) × (brick height + joint)), so a standard modular brick with a 3/8-inch mortar joint works out to the well-known 6.86 bricks per square foot — a 100 ft² wall is 686 bricks, plus a waste allowance and the mortar bags (about 7 per 1000 bricks). The block endpoint does the same for concrete masonry units: a standard 16×8-inch CMU with a 3/8-inch joint is 1.125 blocks per square foot, with roughly 2.5 mortar bags per 100 blocks. Both endpoints take custom unit face dimensions and joint thickness, add a configurable waste percentage and round up to whole units. Everything is computed locally and deterministically, so it is instant and private. Ideal for construction, masonry-contractor, building-supply and home-improvement app developers, takeoff and material-estimating tools, and trade calculators. Pure local computation — no key, no third-party service, instant. Imperial units (inches and square feet). Live, nothing stored. 2 compute endpoints. This is brick/block and mortar estimating; for poured-concrete volume use a concrete API and for drywall use a drywall API.
api.oanor.com/masonry-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Septic System API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Septic System API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Septic System API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Septic System API cost?
Septic System API has a free tier with 100 calls / month. Paid plans start at €15.15 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Septic System API GDPR-compliant?
All requests to Septic System API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/septic-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/septic-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/septic-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);import requests
r = requests.get(
"https://api.oanor.com/septic-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
📌 Pinned
🔒 Locked
·
·
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.