Resistance from temperature
API · /rtd-api
RTD Pt100 Sensor API
RTD (resistance-temperature-detector) sensor maths as an API, computed locally and deterministically with the IEC 60751 Callendar–Van Dusen equation — the resistance, temperature and tolerance numbers an instrumentation or controls engineer reads a Pt100 or Pt1000 with. The resistance endpoint gives the sensor resistance from temperature: above 0 °C, R = R₀·(1 + A·T + B·T²) with A = 3.9083×10⁻³ and B = −5.775×10⁻⁷; below 0 °C a third term adds C·(T−100)·T³ — a standard Pt100 (100 Ω at 0 °C) reads 138.51 Ω at 100 °C and 80.31 Ω at −50 °C, and a Pt1000 is ten times that. The temperature endpoint inverts it to turn a measured resistance back into temperature — analytically above 0 °C, iteratively below — exactly what a transmitter does with the bridge reading, and a reminder that a 3- or 4-wire connection cancels the lead-wire resistance so it does not read as extra degrees. The tolerance endpoint gives the IEC 60751 accuracy band in both °C and Ω by class — AA ±(0.10 + 0.0017·|T|), A ±(0.15 + 0.002·|T|), B ±(0.30 + 0.005·|T|), C ±(0.60 + 0.010·|T|) — the error growing with distance from 0 °C. Everything is computed locally and deterministically, so it is instant and private. Ideal for instrumentation and controls software, data-logger and transmitter firmware, calibration and industrial-IoT tools. Pure local computation — no key, no third-party service, instant. 3 compute endpoints. For NTC thermistors use a thermistor API; for thermocouples a thermocouple API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 84 ms
- Server probes · 24h
- Subscribers
- 4,661
- active
- Total calls
- 76
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 6,050 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 6,050 calls/month
- 2 req/sec
- Resistance + temperature + tolerance
- No credit card
Starter
€10.90 /month
- 61,500 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 61,500 calls/month
- 6 req/sec
- Pt100/Pt1000 & IEC 60751 classes
- Email support
Pro
€34.60 /month
- 253,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 253,000 calls/month
- 15 req/sec
- Transmitter & calibration pipelines
- Priority support
Mega
€107.00 /month
- 1,255,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,255,000 calls/month
- 40 req/sec
- Industrial-IoT scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Thermocouple API
Type-K thermocouple temperature/voltage conversion as an API, computed locally and deterministically from the official NIST ITS-90 reference functions. The voltage endpoint converts a junction temperature in °C to the thermo-electromotive force in millivolts using the NIST type-K direct polynomial (with its Gaussian correction term above 0 °C), and performs cold-junction compensation by subtracting the reference-junction EMF, so a hot junction at 200 °C against a 25 °C terminal block gives the EMF your meter actually reads; a type-K junction produces 4.096 mV at 100 °C and 41.276 mV at 1000 °C against a 0 °C reference. The temperature endpoint does the inverse: it takes the measured EMF in millivolts and the reference-junction temperature, refers the reading back to 0 °C by adding the cold-junction EMF, and returns the hot-junction temperature in °C and K — obtained by numerically inverting the same monotonic forward polynomial, so it is exactly consistent with the forward conversion. Type K (chromel–alumel) covers −270 to 1372 °C. Everything is computed locally and deterministically, so it is instant and private. Ideal for industrial-automation, process-control, data-acquisition, IoT-sensor, furnace and lab-instrument app developers, sensor-linearization and cold-junction-compensation tools, and embedded firmware. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 endpoints. This is the type-K thermocouple; for resistance-temperature detectors use an RTD/PT100 API.
api.oanor.com/thermocouple-api
Load Cell API
Load-cell (weighing-transducer) maths as an API, computed locally and deterministically. The output endpoint computes the bridge output voltage a strain-gauge load cell produces under a given load, Vout = (load/capacity)·sensitivity·excitation, where the full-scale output FSO = sensitivity(mV/V)·excitation(V) is reached at the rated capacity — it returns the output in millivolts, the equivalent mV/V at that load and the capacity utilization, and flags overload. The load endpoint inverts this to recover the applied load from a measured bridge output, load = (Vout/FSO)·capacity. The array endpoint sizes a multi-cell weighing platform: from the number of identical cells, the per-cell capacity and the live and dead (tare) load it returns the evenly distributed per-cell load, its output and utilization and the total system capacity, so cells can be chosen to stay under capacity in the worst case. Sensitivity is in mV/V, excitation in volts (default 10), output in millivolts; load and capacity share any consistent unit. Everything is computed locally and deterministically, so it is instant and private. Ideal for industrial-weighing, scale, force-measurement, silo and process-control app developers, load-cell sizing and calibration tools, and instrumentation education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is load-cell transducer output; for the underlying Wheatstone-bridge and strain maths use a Wheatstone-bridge API.
api.oanor.com/loadcell-api
Wheatstone Bridge API
Wheatstone-bridge and strain-gauge maths as an API, computed locally and deterministically. The bridge endpoint takes the four arm resistances R1–R4 and an excitation voltage and returns the bridge output voltage between the two midpoints, Vout = Vin·(R2/(R1+R2) − R4/(R3+R4)), in volts and millivolts, the voltage at each midpoint, and whether the bridge is balanced (Vout = 0 when R1·R4 = R2·R3). The balance endpoint inverts it: give any three arms and it solves the fourth resistance that balances the bridge, the classic way a Wheatstone bridge measures an unknown resistance. The strain endpoint models a strain-gauge bridge — quarter, half or full — and converts in both directions between mechanical strain and electrical output: from a gauge factor and a strain (given directly, as microstrain or as a relative resistance change ΔR/R = GF·ε) it returns the output ratio and voltage Vout/Vin = (k/4)·GF·ε where k is the number of active arms, and from an output voltage and excitation it returns the strain and microstrain. Everything is computed locally and deterministically, so it is instant and private. Ideal for instrumentation and sensor tools, load-cell, pressure-sensor and RTD measurement design, strain-gauge and data-acquisition apps, and electronics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is bridge and strain-gauge measurement; for Ohm's law, voltage dividers and series/parallel resistor combinations use an Ohm's-law API.
api.oanor.com/wheatstone-api
Newegg API
Live product search from Newegg.com, the major electronics & tech retailer. Search any keyword — laptop, rtx 4070, ssd — and get the product listings with title, brand, model, current price, original price, image, rating, review count, in-stock status, seller and the Newegg product URL. Prices are live USD. Ideal for shopping, price-comparison, deal-tracking and e-commerce dashboards.
api.oanor.com/newegg-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for RTD Pt100 Sensor API?
What's the rate limit for RTD Pt100 Sensor API?
How much does RTD Pt100 Sensor API cost?
Can I cancel my subscription anytime?
Is RTD Pt100 Sensor API GDPR-compliant?
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/rtd-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/rtd-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/rtd-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/rtd-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
·
-
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.