Volume between two cross-sections
API · /earthwork-api
Earthwork Volume API
healthy
3,184 Subscribers
Earthwork volume maths as an API, computed locally and deterministically — the cut/fill-quantity and soil-state numbers a civil engineer, estimator or grading contractor runs for a road, trench or site. The average-end-area endpoint gives the volume between two cross-sections = the mean of the two end areas × the distance between them, ÷ 27 for cubic yards — the everyday earthwork-quantity method you sum section by section down an alignment (a 100 ft²/150 ft² pair 100 ft apart is about 463 cy). The prismoidal endpoint gives the more accurate Simpson volume = length ÷ 6 × (A₁ + 4·A_mid + A₂) using the true middle-section area, preferred for payment quantities where the average-end-area over-estimate would matter. The soil-state endpoint converts between the three states earth passes through: loose = bank × (1 + swell %) (excavating loosens it, ~25 %, so you haul more cubic yards than you cut) and compacted = bank × (1 − shrinkage %) (placing and compacting shrinks it, ~10 %) — which is why a balanced cut-and-fill needs more bank cut than the compacted fill, with the load factor for truck sizing. Everything is computed locally and deterministically, so it is instant and private. Ideal for grading and site-work estimating, surveying and civil-design tools, and earthmoving calculators. Pure local computation — no key, no third-party service, instant. US units (ft², ft, cy). 3 compute endpoints. For tank/storage volumes use a tank API; for concrete mix a concrete API.
api.oanor.com/earthwork-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 77 ms
- Server probes · 24h
- Subscribers
- 3,184
- active
- Total calls
- 76
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 5,100 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 5,100 calls/month
- 2 req/sec
- AEA + prismoidal + soil state
- No credit card
Starter
€12.10 /month
- 52,500 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 52,500 calls/month
- 6 req/sec
- Swell/shrinkage & load factor
- Email support
Pro
€38.10 /month
- 222,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 222,000 calls/month
- 15 req/sec
- Grading-estimate & CAD pipelines
- Priority support
Mega
€118.20 /month
- 1,135,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,135,000 calls/month
- 40 req/sec
- Firm & DOT scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Highway Vertical Curve API
Vertical (parabolic) road-curve geometry as an API, computed locally and deterministically — the K-value, profile-elevation and design-length numbers a highway engineer or surveyor lays a crest or sag curve out with. The geometry endpoint takes the incoming and outgoing grades and the length and returns the algebraic grade difference A = g2 − g1 (negative is a crest, positive a sag), the K value = length ÷ |A| (the headline number on every design chart), the high or low point offset −g1·L/A from the PVC, and — given the PVI station and elevation — the PVC and PVT coordinates and the turning-point station and elevation. The elevation endpoint evaluates the parabola at any station: elevation = PVC elevation + (g1/100)·x + (A/(200·L))·x², with the instantaneous grade g1 + (A/L)·x that sweeps smoothly from g1 to g2 — the smooth change of grade that makes the ride and sight line comfortable. The min-length endpoint gives the AASHTO minimum length for stopping sight distance: crest L = A·S² ÷ 2158 and sag (headlight) L = A·S² ÷ (400 + 3.5·S), with the controlling K, because a crest hides the road over the hump and a sag limits the headlight reach at night. Everything is computed locally and deterministically, so it is instant and private. Ideal for highway- and rail-design tools, surveying and civil-engineering utilities, and CAD/GIS profile work. Pure local computation — no key, no third-party service, instant. US units (ft, %, mph). 3 compute endpoints. For horizontal curves use a horizontal-curve API; for slope conversion a slope API.
api.oanor.com/verticalcurve-api
Highway Horizontal Curve API
Horizontal road-curve geometry as an API, computed locally and deterministically — the curve-element, stationing and design-radius numbers a highway engineer, surveyor or civil-design tool lays out a road or railway curve with. The geometry endpoint takes the radius and the intersection (deflection) angle and returns the full simple circular curve: the tangent T = R·tan(Δ/2), the curve length L = R·Δ in radians, the long chord LC = 2R·sin(Δ/2), the middle ordinate M = R(1−cos(Δ/2)) and the external distance E = R(sec(Δ/2)−1), plus the degree of curve (arc definition) = 5729.578 ÷ R, the US shorthand for sharpness. The stations endpoint lays the curve out from the PI: the PC (point of curvature) = PI − tangent and the PT (point of tangency) = PC + curve length — and it reminds you the PT is reached along the arc, not by adding the tangent again. The min-radius endpoint gives the minimum radius for a design speed (AASHTO) R = V² ÷ (15·(e + f)), where e is the superelevation and f the side-friction factor, the banking-plus-grip that holds a vehicle in the turn. Everything is computed locally and deterministically, so it is instant and private. Ideal for highway- and rail-design tools, surveying and civil-engineering utilities, and CAD/GIS road layout. Pure local computation — no key, no third-party service, instant. US units (ft, mph). 3 compute endpoints. For slope and grade use a slope API; for open-channel drainage a Manning API.
api.oanor.com/horizontalcurve-api
Soil Bearing Capacity API
Geotechnical foundation maths as an API, computed locally and deterministically. The factors endpoint computes the Terzaghi/Vesic bearing-capacity factors Nc, Nq and Nγ from a soil friction angle — Nq = e^(π·tanφ)·tan²(45+φ/2), Nc = (Nq−1)·cotφ and Nγ = 2(Nq+1)·tanφ. The bearing-capacity endpoint computes the ultimate, net and allowable bearing capacity of a strip, square or circular footing from the cohesion, friction angle, soil unit weight, footing width and founding depth, qu = sc·c·Nc + γ·D·Nq + sγ·γ·B·Nγ, breaking it into its cohesion, surcharge and self-weight components and dividing by a factor of safety (default 3) for the allowable value. The settlement endpoint computes the immediate elastic settlement of a footing, s = q·B·(1−ν²)·I / E, from the applied pressure, the footing width, the soil elastic modulus and Poisson's ratio. Cohesion and pressures are in kilopascals, unit weight in kN/m³ and lengths in metres. Everything is computed locally and deterministically, so it is instant and private. Ideal for civil-engineering, geotechnical, foundation-design and construction app developers, footing-sizing and feasibility tools, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is foundation bearing capacity; for lateral earth pressure on walls use an earth-pressure API and for open-channel flow a Manning API.
api.oanor.com/soil-api
Rebar Calculator API
Reinforcement-steel (rebar) maths as an API, computed locally and deterministically. The area endpoint computes the cross-sectional area of a reinforcing bar, a = π/4·d², its mass per metre (a·7850/1e6, steel ρ = 7850 kg/m³), the total area and mass for a number of bars, and — given a required steel area — the number of bars needed and the area provided. The spacing endpoint lays out bars across a section: from the width, the cover, the bar diameter and either a centre-to-centre spacing or a bar count it returns the other, n = floor((width − 2·cover − d)/spacing) + 1, the total steel area and the area per metre of width. The ratio endpoint computes the reinforcement ratio ρ = As/(b·d) of a section from the steel area (or the bars) and the section width and effective depth, as a fraction and a percentage, the single number that governs whether a beam is under- or over-reinforced. Everything is computed locally and deterministically, so it is instant and private. Ideal for structural and site-engineering tools, reinforced-concrete detailing, bar-bending schedules and steel take-off, and civil-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is rebar geometry and quantities; for concrete mix proportions use a concrete API.
api.oanor.com/rebar-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Earthwork Volume API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Earthwork Volume API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Earthwork Volume 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 Earthwork Volume API cost?
Earthwork Volume API has a free tier with 100 calls / month. Paid plans start at €12.10 / 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 Earthwork Volume API GDPR-compliant?
All requests to Earthwork Volume 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/earthwork-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/earthwork-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/earthwork-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/earthwork-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.