Linear thermal expansion
API · /thermalexpansion-api
Thermal Expansion API
healthy
4,920 Subscribers
Thermal-expansion maths as an API, computed locally and deterministically. The linear endpoint computes how much a solid grows or shrinks when its temperature changes, ΔL = α·L0·ΔT, returning the change in length and the new length from an original length, a temperature change (given directly or as an initial and final temperature) and the linear expansion coefficient α — taken from a built-in material table (steel, aluminium, copper, concrete, glass, invar and more) or supplied directly; lengths accept metres, centimetres, millimetres, feet or inches. The volume endpoint computes volumetric expansion, ΔV = β·V0·ΔT, where for a solid the volumetric coefficient is β ≈ 3α and for a liquid (water, ethanol, mercury, petrol and others) β is taken directly; volumes accept cubic metres, litres, millilitres or cubic feet. The materials endpoint lists the coefficients. A negative temperature change gives contraction. Everything is computed locally and deterministically, so it is instant and private. Ideal for civil and mechanical engineering tools, rail, pipe and bridge expansion-gap design, manufacturing-tolerance and HVAC apps, and physics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is thermal expansion; for heat energy and temperature change use a specific-heat API.
api.oanor.com/thermalexpansion-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 91 ms
- Server probes · 24h
- Subscribers
- 4,920
- active
- Total calls
- 32
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 2,000 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- Linear thermal expansion (delta-L) endpoint
- Built-in coefficients for common metals
- 2 req/s, deterministic results
Starter
€9.00 /month
- 25,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- Linear + area + volumetric expansion endpoints
- Full material coefficient library
- Custom alpha override input
- Email support
Pro
€24.00 /month
- 150,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- All expansion modes + expansion-gap sizing
- Multi-segment pipe/rail batch compute
- Temperature-range stress estimates
- Priority support, 99.9% uptime
Mega
€75.00 /month
- 1,024,000 calls / month
- 60 requests / second
- Hard cap (429 above quota, no overage)
- Highest throughput for CAD/PLM integrations
- Batch material sweeps in one call
- Custom coefficient datasets
- Dedicated support + SLA
Built by
Related APIs
Other APIs with overlapping tags.
Vapor Pressure API
Vapor-pressure thermodynamics as an API, computed locally and deterministically. The clausius-clapeyron endpoint predicts the vapor pressure of a substance at a new temperature from a known reference point and the molar enthalpy of vaporization, using ln(P2/P1) = -ΔHvap/R·(1/T2 - 1/T1) with temperatures in kelvin — so from water boiling at 101.325 kPa at 373.15 K and ΔHvap ≈ 40.66 kJ/mol it returns about 42.6 kPa at 350 K. The enthalpy endpoint inverts the same relation: given two pressure/temperature points it solves for the molar enthalpy of vaporization, ΔHvap = -R·ln(P2/P1)/(1/T2 - 1/T1), in J/mol and kJ/mol. The antoine endpoint evaluates the Antoine equation log10(P) = A - B/(C + T) both ways — supply a temperature to get the vapor pressure, or a pressure to get the boiling temperature — defaulting to the water constants (°C and mmHg, so water reads 760 mmHg at 100 °C) but accepting any A, B, C for other substances. The gas constant R = 8.314462618 J/(mol·K). Everything is computed locally and deterministically, so it is instant and private. Ideal for chemical-engineering, process-simulation, distillation, HVAC, meteorology and chemistry-education app developers, boiling-point and phase-equilibrium tools, and lab software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is vapor pressure and boiling point; for humidity and dew point use a psychrometric API and for ideal-gas state use a gas-law API.
api.oanor.com/vaporpressure-api
Carnot Heat Engine API
Heat-engine efficiency and coefficient of performance as an API, computed locally and deterministically. The efficiency endpoint gives the Carnot maximum efficiency of any heat engine working between two temperatures, η = 1 − Tc/Th (in kelvin) — the absolute upper limit no real engine can beat — and, given a heat input, the maximum work it could produce and the heat it must reject. The heat-pump endpoint gives the Carnot coefficient of performance of a heat pump, COP = Th/(Th − Tc), and of a refrigerator or air conditioner, COP = Tc/(Th − Tc), and the heat moved for a given work input. The engine endpoint analyses a real engine from its heat balance: from any two of the heat input, the work output, the efficiency or the heat rejected it returns the rest using η = W/Qh and Qc = Qh − W, and — given the reservoir temperatures — compares it to the Carnot limit and reports the second-law (exergy) efficiency. Temperatures accept kelvin, Celsius or Fahrenheit. Everything is computed locally and deterministically, so it is instant and private. Ideal for thermodynamics-education tools, engine, turbine and HVAC design, refrigeration and heat-pump apps, and energy-systems software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is heat-engine and refrigeration-cycle efficiency; for sensible heat use a specific-heat API and for heat-exchanger LMTD use a heat-exchanger API.
api.oanor.com/carnot-api
Newton Cooling & Convection API
Newton's law of cooling and convective heat transfer as an API, computed locally and deterministically. The convection endpoint applies the convective-heat-transfer rate Q = h·A·ΔT — the heat carried away from a surface equals the convection coefficient times the area times the temperature difference between the surface and the fluid — and solves for whichever of the heat rate, the coefficient, the area or the temperature difference you leave out, with typical coefficients for natural and forced air, water, boiling and condensing built in. The cooling endpoint applies Newton's law of cooling, T(t) = T_env + (T0 − T_env)·e^(−k·t): from an initial temperature, the ambient temperature and a cooling constant (or time constant τ = 1/k) it gives the temperature after a time, or the time to reach a target temperature, or it solves the cooling constant from a measured temperature at a known time — the maths behind how a hot drink, a forensic body or a cooling casting approaches room temperature. The coefficient endpoint links the cooling constant to the physical properties, k = h·A/(m·c), and the thermal time constant. Everything is computed locally and deterministically, so it is instant and private. Ideal for thermal-engineering and HVAC tools, food-safety and forensic cooling apps, electronics-cooling and process-control software, and physics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is convection and transient cooling; for steady conduction through walls use a U-value API and for thermal radiation use a Stefan-Boltzmann API.
api.oanor.com/cooling-api
Heat Exchanger LMTD API
Heat-exchanger LMTD and effectiveness-NTU maths as an API, computed locally and deterministically. The lmtd endpoint computes the log mean temperature difference, LMTD = (ΔT1 − ΔT2)/ln(ΔT1/ΔT2), the true average driving temperature of a heat exchanger, from the hot and cold stream inlet and outlet temperatures for either a counterflow or a parallel-flow arrangement, and flags a temperature cross. The duty endpoint applies Q = U·A·LMTD·F — the heat duty equals the overall heat-transfer coefficient times the area times the LMTD times an optional correction factor — and solves for whichever of the duty, the coefficient, the area or the LMTD you leave out, taking the LMTD directly or from the four temperatures. The effectiveness endpoint uses the effectiveness-NTU method: from the hot and cold heat-capacity rates (given directly or as mass flow times specific heat) and the number of transfer units NTU = U·A/Cmin, it returns the capacity ratio, the effectiveness for the arrangement, and — given the inlet temperatures — the maximum and actual heat duty and the outlet temperatures. Everything is computed locally and deterministically, so it is instant and private. Ideal for process, chemical and mechanical engineering tools, HVAC, refrigeration and thermal-design apps, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is two-stream heat-exchanger analysis; for the sensible heat of a single stream Q = m·c·ΔT use a specific-heat API.
api.oanor.com/lmtd-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Thermal Expansion API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Thermal Expansion API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Thermal Expansion 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 Thermal Expansion API cost?
Thermal Expansion API has a free tier with 100 calls / month. Paid plans start at €9.00 / 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 Thermal Expansion API GDPR-compliant?
All requests to Thermal Expansion 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/thermalexpansion-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/thermalexpansion-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/thermalexpansion-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/thermalexpansion-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.