Lumens / watts / efficacy
API · /lighting-api
Lighting Calculator API
salutare
4,612 Abbonati
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.
api.oanor.com/lighting-api
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 80 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,612
- attiva
- Chiamate totali
- 76
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 10,335 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 10,335 calls/month
- 2 req/sec
- Room + lux + efficacy
- No credit card
Starter
€11.85 /mese
- 19,950 chiamate/mese
- 8 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 19.95k llamadas/mes
- 8 req/seg
- Ajustes predefinidos de sala + footcandles
- Soporte por correo electrónico
Pro
€31.75 /mese
- 249,500 chiamate/mese
- 20 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 249.5k llamadas/mes
- 20 req/seg
- Tuberías de iluminación / eléctricas
- Soporte prioritario
Mega
€69.75 /mese
- 1,290,000 chiamate/mese
- 50 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1.29M calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
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
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
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
Sauna-Heizer-Berechnungen als API, lokal und deterministisch berechnet – die Heizleistung, Steinmasse und elektrischen Werte, die ein Saunabauer, Installateur oder Wellnesshändler für eine Kabine dimensioniert. Der Heizgrößen-Endpoint gibt die Leistung: etwa 1 kW pro 1,3 m³ gut isolierter Kabine (Raumvolumen ÷ 1,3), wobei kalte Oberflächen, die der Heizer ebenfalls erwärmen muss – eine Glastür oder -wand, nackter Stein, Fliesen oder ungedämmtes Holz – etwa 1,2 m³ äquivalentes Volumen pro Quadratmeter hinzufügen, sodass ein 10 m³ Raum mit einer 2 m² Glastür etwa einen 10 kW Heizer benötigt, aufgerundet auf die nächste Standardgröße. Der Steine-Endpoint gibt die empfohlene Saunasteinmasse, etwa 10–20 kg pro kW (mehr Steine für einen weicheren, dampfigen Löyly, weniger für eine schnellere Aufheizzeit), mit einem Hinweis, richtige Peridotit/Olivin-Steine locker gestapelt zu verwenden. Der Elektrik-Endpoint gibt den Strom an, den der Widerstandsheizer zieht – Leistung ÷ Spannung für einphasig oder ÷ (√3 × Spannung) für dreiphasig, da die meisten Heizer über ~4 kW dreiphasig angeschlossen werden, um den Strom pro Leitung und Kabelquerschnitt gering zu halten – zur Dimensionierung des Schutzschalters und des dedizierten FI-geschützten Stromkreises. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Sauna- und Wellnesshändler, Heimwerker- und DIY-Tools sowie HLK-/Elektro-Schätzungs-Apps. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Schätzungen – folgen Sie der Tabelle des Heizerherstellers und den örtlichen Elektrovorschriften. 3 Compute-Endpoints. Für Dampfkesselberechnungen verwenden Sie eine Boiler-API; für Raumwärmeverlust eine U-Wert-API.
api.oanor.com/saunaheater-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Lighting Calculator API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Lighting Calculator API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Lighting Calculator API?
Il piano gratuito consente 1 richiesta al secondo. I piani a pagamento arrivano fino a 50 richieste al secondo nel piano Mega. I limiti rigorosi restituiscono HTTP 429 oltre la quota — nessuna spesa imprevista.
Quanto costa Lighting Calculator API?
Lighting Calculator API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €11.85 / mese con quote più alte e limiti di velocità più rapidi.
Posso cancellare l'abbonamento in qualsiasi momento?
Sì. I piani sono fatturati mensilmente e puoi cancellare in qualsiasi momento dalla dashboard di fatturazione. Nessun contratto a lungo termine e nessuna penale di cancellazione.
Lighting Calculator API è conforme al GDPR?
Tutte le richieste a Lighting Calculator API passano attraverso il nostro gateway in UE. La tua chiave upstream non lascia mai il nostro server e nessun dato personale viene condiviso con il fornitore upstream oltre alla richiesta inviata.
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo 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())Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
📌 Fissato
🔒 Bloccato
·
·
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.