oanor
Sign up free
Marketplace Pricing Features Sign in

API · /lighting-api

Lighting Calculator API

healthy 4,612 Subscribers

Lighting design maths as an API, computed locally and deterministically. The room endpoint works out how many lumens a room needs from its area and a target illuminance — given directly in lux or chosen from a room-type preset (living, kitchen, office, workshop and more) — and, optionally, how many fixtures at a given lumen output and how many watts at a given lamp type. The lux endpoint converts between lux, footcandles and lumens over an area, so you can find the illuminance from a light output and a room size or vice versa. The efficacy endpoint relates lumens, watts and luminous efficacy (lumens per watt): give any two — or a lamp-type preset such as incandescent, halogen, CFL or LED — and it computes the third. Everything is computed locally and deterministically, so it is instant and private. It is a lumen-method estimate: target levels are typical guidance (EN 12464 / IES) and a full design would add room and utilisation factors. Ideal for lighting and electrical tools, interior-design and home apps, retrofit and energy-saving calculators, and smart-home planning. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is illumination maths; for Ohm's-law electrical quantities use an electronics API.

#lighting #lumens #lux #illuminance #electrical #developer-tools
api.oanor.com/lighting-api
Get an API key Try in playground → Contact provider

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

/api/lighting-api/openapi.json
/api/lighting-api/llms.txt

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

Lighting Calculator API — live data on the oanor API marketplace

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
80 ms
Server probes · 24h
Subscribers
4,612
active
Total calls
76
last 7 days
status Full status page → · 12 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 10,335 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 10,335 calls/month
  • 2 req/sec
  • Room + lux + efficacy
  • No credit card
Sign in to subscribe

Starter

€11.85 /month

  • 19,950 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 19.95k calls/month
  • 8 req/sec
  • Room presets + footcandles
  • Email support
Sign in to subscribe

Pro

€31.75 /month

  • 249,500 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 249.5k calls/month
  • 20 req/sec
  • Lighting / electrical pipelines
  • Priority support
Sign in to subscribe

Mega

€69.75 /month

  • 1,290,000 calls / month
  • 50 requests / second
  • Hard cap (429 above quota, no overage)
  • 1.29M calls/month
  • 50 req/sec
  • Platform scale
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

Photometry & Lighting API — oanor API marketplace

Photometry & Lighting API

Photometry and lighting maths as an API, computed locally and deterministically. The illuminance endpoint computes the light falling on a surface from a point source, E = I·cos(θ)/d² in lux, from the luminous intensity in candela, the distance in metres and the angle of incidence from the surface normal — a 1000 cd source straight down at 2 m gives 250 lux. The inverse-square endpoint scales a known illuminance to a new distance, E2 = E1·(d1/d2)², so doubling the distance quarters the light. The flux-intensity endpoint converts between luminous flux in lumens and luminous intensity in candela through the solid angle, I = Φ/Ω and Φ = I·Ω, with the solid angle taken as the full sphere 4π steradian for an isotropic source or, for a spotlight of full beam angle β, Ω = 2π·(1 − cos(β/2)) — so a 100 cd isotropic source emits about 1256.6 lm, and a 1000 cd lamp in a 30° beam emits about 214 lm. Distances are in metres and angles in degrees. Everything is computed locally and deterministically, so it is instant and private. Ideal for lighting-design, architecture, photography, film, horticulture-grow-light, stage and AV app developers, lux-and-lumen and luminaire-planning tools, and engineering software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. These are photometric (perceived-light) quantities; for blackbody/peak-wavelength radiometry use a Wien/radiation API.

api.oanor.com/photometry-api

 Color Temperature API — oanor API marketplace

Color Temperature API

Turn physical light into RGB colours — entirely locally. The kelvin endpoint converts a colour temperature in Kelvin into the RGB colour of a black body at that temperature: warm candle and incandescent tones below 3000 K, neutral and daylight whites around 5000–6500 K, and cool bluish light above, using Tanner Helland's widely-used approximation and returning hex, an rgb() string and a plain-English description (candlelight, warm white, neutral, daylight, cool). The wavelength endpoint converts a wavelength of visible light in nanometres (380–780 nm) into the approximate RGB colour the human eye perceives, with the natural intensity fall-off at the violet and red edges of the spectrum, and names the band (violet, blue, cyan, green, yellow, orange, red). Everything is computed locally and deterministically, so it is instant and private. Ideal for lighting and smart-bulb apps, photography and white-balance tools, data-visualisation of temperature or spectra, theming and UI accents, and science and education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. These are perceptual approximations, not colorimetric CIE conversions; for hex/RGB/HSL conversion and palettes use a colour API.

api.oanor.com/colortemp-api

 Stellar (XLM) On-Chain API — oanor API marketplace

Stellar (XLM) On-Chain API

Live on-chain data from the Stellar network, the open blockchain for payments and asset issuance behind the lumen (XLM), served straight from Stellar's public Horizon API — no key, nothing cached. The account endpoint returns any address's full wallet: its XLM balance and every issued asset it holds — Stellar is the home of anchored stablecoins like USDC, so a wallet shows native lumens alongside its tokens, each with the asset code, issuer and balance — plus the account sequence, sub-entry count and home domain. The payments endpoint returns the account's most recent payments in and out, each with the counterparty, asset, amount and time. The transactions endpoint returns the account's recent transactions with the ledger, fee, operation count, success flag and memo. The network endpoint returns the live state of the network itself: the latest ledger, the base fee and the fee percentiles and ledger capacity that tell you how congested the network is. Everything is read live from Horizon, nothing stored. This is the Stellar on-chain layer for any wallet, anchor, exchange, payments or analytics app. Distinct from the XRP Ledger, EVM and Solana on-chain APIs and from price feeds — this is Stellar account state, multi-asset balances, payments and network health. 4 endpoints, no key on our side.

api.oanor.com/stellar-api

 Sauna Heater API — oanor API marketplace

Sauna Heater API

Sauna-heater sizing maths as an API, computed locally and deterministically — the heater-power, stone-mass and electrical numbers a sauna builder, installer or wellness retailer sizes a cabin with. The heater-size endpoint gives the power: about 1 kW per 1.3 m³ of well-insulated cabin (room volume ÷ 1.3), with cold surfaces the heater must also warm — a glass door or wall, bare stone, tile or uninsulated timber — adding roughly 1.2 m³ of equivalent volume per square metre, so a 10 m³ room with a 2 m² glass door wants about a 10 kW heater, rounded up to the next standard size. The stones endpoint gives the recommended sauna-stone mass, roughly 10–20 kg per kW (more stones for a softer, steamier löyly, fewer for a faster warm-up), with a note to use proper peridotite/olivine stones stacked loosely. The electrical endpoint gives the current the resistive heater draws — power ÷ voltage for single-phase or ÷ (√3 × voltage) for three-phase, since most heaters above ~4 kW are wired three-phase to keep the per-leg current and cable size down — to size the breaker and the dedicated RCD-protected circuit. Everything is computed locally and deterministically, so it is instant and private. Ideal for sauna and wellness retailers, home-improvement and DIY tools, and HVAC/electrical estimating apps. Pure local computation — no key, no third-party service, instant. Estimates — follow the heater maker's chart and local wiring code. 3 compute endpoints. For steam-boiler maths use a boiler API; for room heat loss a U-value API.

api.oanor.com/saunaheater-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

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