API · /loadcell-api

Load Cell API

healthy 4,972 Subscribers

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.

#load-cell #weighing #force #transducer #instrumentation #developer-tools

api.oanor.com/loadcell-api

Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/loadcell-api/openapi.json

/api/loadcell-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy

Uptime: 100.00%; Server probes · 24h
Avg latency: 88 ms; Server probes · 24h
Subscribers: 4,972; active
Total calls: 20; last 7 days

Full status page → · 24 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

2,200 calls / month
2 requests / second
Hard cap (429 above quota, no overage)
2,200 calls/month
2 req/sec
Output + load + array
No credit card

Starter

€10.00 /month

46,000 calls / month
6 requests / second
Hard cap (429 above quota, no overage)
46,000 calls/month
6 req/sec
Full-scale output, utilization, overload
Email support

Pro

€24.00 /month

270,000 calls / month
15 requests / second
Hard cap (429 above quota, no overage)
270,000 calls/month
15 req/sec
Multi-cell platform & calibration pipelines
Priority support

Mega

€74.00 /month

1,650,000 calls / month
40 requests / second
Hard cap (429 above quota, no overage)
1,650,000 calls/month
40 req/sec
Platform scale
Dedicated SLA

Built by

PremiumApi

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

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

Beekeeping API

Beekeeping and apiary maths as an API, computed locally and deterministically — the mite, brood and winter-stores numbers a beekeeper manages a hive with. The varroa endpoint turns an alcohol-wash or sugar-shake count into the infestation rate: mites per 100 bees = mite count ÷ bees sampled × 100, where a half-cup scoop is about 300 bees, and it flags when the colony crosses the treatment threshold (commonly 3 mites per 100 bees, or 3 %). The brood endpoint projects the development calendar from the day an egg is laid: it hatches around day 3, the cell is capped around day 8–10 and the adult emerges on day 16 for a queen, 21 for a worker and 24 for a drone — so a worker egg laid on the 1st emerges three weeks later. The stores endpoint sizes winter honey: how many kilograms the colony needs by climate (about 12 kg mild to 35 kg harsh), the equivalent full deep frames (~2.25 kg each), and the deficit and frames to feed against the current stores. Date arithmetic is exact. Everything is computed locally and deterministically, so it is instant and private. Ideal for beekeeping, apiary-management, homestead and agriculture app developers, hive-inspection and mite-monitoring tools, and beekeeping education. Pure local computation — no key, no third-party service, instant. Dates as YYYY-MM-DD; metric weights. Live, nothing stored. 3 compute endpoints. A planning aid — local conditions vary.

api.oanor.com/apiary-api

Maple Syrup API

Maple-syrup making maths as an API, computed locally and deterministically — the sap-to-syrup yield and finishing numbers a sugarmaker plans a season around. The yield endpoint takes the volume of sap and its sugar content in °Brix and returns the syrup it makes from the sugar balance (syrup = sap × sap °Brix / finished °Brix, finishing at 66.9 °Brix), the water that has to boil off, the sap-to-syrup ratio, and the classic Jones' Rule of 86 (86 ÷ sap °Brix) — the field rule that famously gives about 43 litres of 2 % sap per litre of syrup. The finish endpoint gives the boil-off finishing temperature: syrup is done about 4 °C (7.1 °F) above the boiling point of water, so at sea level that is ~104 °C / 219 °F — calibrate to your own water boiling point, which drops with altitude, and finish that many degrees higher; it also returns the finished density (~66.9 °Brix, SG ≈ 1.337). Everything is computed locally and deterministically, so it is instant and private. Ideal for maple-sugaring, homestead, craft-food and farm app developers, evaporator and yield-planning tools, and sugaring education. Pure local computation — no key, no third-party service, instant. Consistent volume units; temperatures in °C or °F. Live, nothing stored. 2 compute endpoints. A planning aid — a hydrometer or refractometer confirms the finish.

api.oanor.com/maple-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Load Cell API?

Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Load Cell API with the x-oanor-key header. No credit card needed for the free tier.

What's the rate limit for Load Cell 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 Load Cell API cost?

Load Cell API has a free tier with 100 calls / month. Paid plans start at €10.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 Load Cell API GDPR-compliant?

All requests to Load Cell 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.

LoadCell 3

Meta 1

Pick an endpoint from the list on the left to see its details and try it.

GET /v1/array

Multi-cell array

Playground

Parameters

Custom headers

Language: Client:

GET /v1/load

Load from output

Playground

Parameters

Custom headers

Language: Client:

GET /v1/output

Bridge output

Playground

Parameters

Custom headers

Language: Client:

GET /v1/meta

Spec

Playground

Custom headers

Language: Client:

Code snippets

curl https://api.oanor.com/loadcell-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."

const res = await fetch("https://api.oanor.com/loadcell-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();

$ch = curl_init("https://api.oanor.com/loadcell-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/loadcell-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

New thread

📌 Pinned 🔒 Locked

· ·

🔒 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.

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.

Pick a key

Plaintext is shown once at creation — use the prefix as a reminder.

Load Cell API

API health

Pricing

Built by

Related APIs

Thermocouple API

Wheatstone Bridge API

Beekeeping API

Maple Syrup API

Frequently asked questions

Parameters

Parameters

Parameters

Code snippets

Ratings

Discussion

New thread

📌 🔒

Support

Open new ticket

Your cookie choices