API · /bolttorque-api

Bolt Torque API

healthy 3,966 Subscribers

Bolted-joint torque, preload and stress maths as an API, computed locally and deterministically for ISO metric fasteners. The torque endpoint applies the torque-tension relation T = K·D·F — the tightening torque equals the nut factor times the nominal diameter times the bolt preload — and solves either way: the torque needed for a target preload, or the preload achieved by a given torque, with the nut factor K capturing the lubrication condition (≈0.20 plain, 0.16 plated, 0.12 lubricated). The stressarea endpoint computes the tensile stress area from the thread geometry, As = π/4·(d − 0.9382·P)² — the effective cross-section that carries the load — together with the nominal shank area and, given a proof or yield stress, the proof and yield loads of the bolt. The preload endpoint sets the clamp force as a percentage of the proof load (75 % is the usual target for reusable joints), F = (percent/100)·σproof·As, and returns the resulting tensile stress and, with a diameter and nut factor, the tightening torque. Grade proof stresses for 8.8, 10.9 and 12.9 bolts are documented. Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical-design, assembly and maintenance tools, torque-spec generation, fastener selection and structural-bolting apps, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is bolt tightening and preload mechanics; for thread pitch/lead geometry use a thread API and for bolt-circle hole patterns use a bolt-circle API.

api.oanor.com/bolttorque-api
Get an API key Try in playground → Contact provider

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

/api/bolttorque-api/openapi.json
/api/bolttorque-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
3,966
active
Total calls
36
last 7 days
status Full status page → · 24 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 2,000 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • Torque-to-preload for ISO metric coarse threads
  • Single friction-coefficient (K-factor) input
  • Deterministic results, no upstream latency
  • 2 req/s burst
Sign in to subscribe

Starter

€9.00 /month

  • 25,000 calls / month
  • 5 requests / second
  • Hard cap (429 above quota, no overage)
  • Full torque, preload and bolt-stress endpoints
  • ISO metric coarse + fine thread tables
  • Configurable thread + head friction coefficients
  • Yield-utilisation percentage output
Sign in to subscribe

Pro

€24.00 /month

  • 150,000 calls / month
  • 15 requests / second
  • Hard cap (429 above quota, no overage)
  • Batch joint calculations in one call
  • Tightening-factor and scatter-band ranges
  • Property-class 8.8/10.9/12.9 stress checks
  • Clamp-load and stretch (elongation) outputs
Sign in to subscribe

Mega

€75.00 /month

  • 1,000,000 calls / month
  • 40 requests / second
  • Hard cap (429 above quota, no overage)
  • High-volume CAE/PLM integration throughput
  • Full ISO fastener library + custom geometries
  • Combined preload + applied-load safety margins
  • Priority support and 40 req/s sustained
Sign in to subscribe

Built by

Related APIs

Other APIs with overlapping tags.

Screw Thread API

Screw-thread geometry as an API, computed locally and deterministically for the 60° ISO metric and Unified (UTS) thread form. The pitch endpoint converts between the thread pitch in millimetres and threads per inch (TPI = 25.4 ÷ pitch) and works out the lead — the distance the thread advances in one turn — from the pitch and the number of starts. The dimensions endpoint takes a nominal (major) diameter and a pitch and returns the full set of thread diameters and heights: the fundamental triangle height, the external thread height, the pitch diameter (D − 0.6495·P), the external minor diameter (D − 1.2269·P) and the internal minor diameter (D − 1.0825·P), in both millimetres and inches. The tapdrill endpoint gives the drill size for cutting an internal thread: the standard metric rule of nominal diameter minus pitch (about 75–83% thread), the resulting thread engagement, and — for a target engagement percentage — the matching drill size. Diameters accept millimetres or inches, and threads can be specified by pitch or by TPI. Everything is computed locally and deterministically, so it is instant and private. Ideal for machining and CNC tools, mechanical-design and CAD apps, maker and 3D-printing projects, and hardware and fastener catalogues. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is screw-thread geometry; for the torque to tighten a bolt use a torque API.

api.oanor.com/thread-api

Bolt Torque API

Bolt and fastener torque maths as an API, using the standard short-form relation T = K · D · F — torque equals the nut factor times the bolt diameter times the clamp load (preload). The torque endpoint computes the tightening torque, in newton-metres, foot-pounds, inch-pounds and kilogram-force metres, from the bolt diameter, the target clamp load and a nut factor — given directly or chosen from a condition preset (dry, lubricated, zinc-plated, galvanized, waxed and more). The preload endpoint solves the inverse: the clamp load a given torque produces on a bolt of a given diameter and friction. The convert endpoint converts a torque value between newton-metres, foot-pounds, inch-pounds and kilogram-force metres. Everything is computed locally and deterministically, so it is instant and private. The K·D·F short form is an estimate that depends heavily on friction — it is engineering guidance only, so always follow the manufacturer's torque specification. Ideal for mechanical, automotive and aerospace tools, maker and assembly apps, maintenance and field-service software, and engineering calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is fastener torque; for wire gauge and resistance use a wire-gauge API and for Ohm's law use an electronics API.

api.oanor.com/torque-api

O-Ring Seal API

O-ring seal-design maths as an API, computed locally and deterministically — the squeeze, gland and stretch numbers an engineer or maker designs a seal to. The squeeze endpoint gives the compression that makes the seal: squeeze = (cross-section − gland depth) ÷ cross-section, so a 0.139-inch cord in a 0.113-inch deep groove is squeezed 18.7 %, and it grades the result — roughly 10–16 % suits dynamic (reciprocating) seals and 15–30 % static ones — and, given the groove width, the gland fill percentage, which should stay under about 85 % so the rubber has room to expand from heat or fluid swell. The gland endpoint works the other way: from the cross-section and whether the seal is static or dynamic (or a target squeeze) it returns the groove depth and a width sized for about 70 % fill — typically 1.3 to 1.5 times the cross-section — plus a corner radius. The stretch endpoint checks installation: stretch = (mating diameter − o-ring ID) ÷ ID, which should stay under about 5 % on a rod because stretching thins the cross-section and steals squeeze. Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical-engineering, hydraulics, pneumatics, vacuum and product-design app developers, seal-selection and gland-design tools, and CAD plugins. Pure local computation — no key, no third-party service, instant. Inches or millimetres. Live, nothing stored. 3 compute endpoints.

api.oanor.com/oring-api

Gear Ratio API

Gear-train ratio, speed and torque maths as an API, computed locally and deterministically. The ratio endpoint computes the gear ratio of a single pair from the driver and driven tooth counts (or pitch diameters), ratio = N_driven/N_driver, classifies it as a reduction (more torque, less speed) or an overdrive, and — given an input speed and torque — returns the output speed (input/ratio) and the output torque (input·ratio·efficiency). The train endpoint computes a compound gear train: the overall ratio is the product of the individual stage ratios, and it returns each stage ratio, the output speed and torque, noting that idler gears change only the direction of rotation, not the ratio. The solve endpoint finds the missing one of the input speed, the output speed and the ratio from the other two — for example, the ratio needed to drop a 1500 rpm motor to a 500 rpm output. Everything is computed locally and deterministically, so it is instant and private. Ideal for drivetrain, robotics and machine-design tools, gearbox and transmission selection, bicycle and vehicle gearing, and mechanical-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is gear-train ratio and torque; for spur-gear tooth geometry use a spur-gear API.

api.oanor.com/gearratio-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Bolt Torque API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Bolt Torque API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Bolt Torque 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 Bolt Torque API cost?
Bolt Torque 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 Bolt Torque API GDPR-compliant?
All requests to Bolt Torque 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/bolttorque-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/bolttorque-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/bolttorque-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/bolttorque-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 in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

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

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.