Pellets for a heat demand
API · /pellet-api
Wood Pellet API
Wood-pellet heating maths as an API, computed locally and deterministically — the consumption, heat-output and storage numbers a homeowner, installer or heating planner sizes a pellet system by. The consumption endpoint gives the pellets to meet a heat demand = the demand ÷ the usable heat per kilo, where usable = the calorific value × the boiler efficiency: ENplus wood pellets hold about 4.8 kWh/kg and a modern pellet boiler runs ~90 %, so each kilo delivers roughly 4.3 kWh — a 10,000 kWh annual demand then needs about 2.3 tonnes of pellets, around 154 fifteen-kilo bags or a bulk delivery. The heat-output endpoint inverts it: the usable heat from a mass = mass × calorific value × efficiency, so a tonne of ENplus pellets is about 4,800 kWh gross of which a 90 % boiler delivers ~4,320 kWh — the equivalent of roughly 480 litres of heating oil or 432 m³ of natural gas. The storage-volume endpoint sizes the hopper or silo: storage = the pellet mass ÷ the bulk (poured) density, about 650 kg/m³ for ENplus, so 2.3 tonnes fill roughly 3.6 m³ — size the store for the full delivery plus headroom for the fill pipe. Everything is computed locally and deterministically, so it is instant and private. Ideal for pellet-heating and installer tools, home-energy and quoting apps, and renewable-heat calculators. Pure local computation — no key, no third-party service, instant. Uses standard ENplus figures — set your own for a specific pellet grade. 3 compute endpoints. For cordwood use a firewood API; for propane/LPG a propane API.
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 108 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,070
- attiva
- Chiamate totali
- 4
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 7,350 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 7.350 Aufrufe/Monat
- 2 req/sec
- Verbrauch + Wärmeabgabe + Speicherung
- Keine Kreditkarte
Starter
€7.15 /mese
- 61,500 chiamate/mese
- 6 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 61.500 Aufrufe/Monat
- 6 req/sec
- Beutelanzahl & Silogrößenbestimmung
- E-Mail-Support
Pro
€24.40 /mese
- 249,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 249.000 Aufrufe/Monat
- 15 req/sec
- Installations- und Angebotspipelines
- Prioritäts-Support
Mega
€76.20 /mese
- 1,155,000 chiamate/mese
- 40 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1.155.000 Aufrufe/Monat
- 40 req/sec
- Plattform- und Versorgungsmaßstab
- Dedizierte SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Radiant Floor API
Radiant-Floor- und Hydronic-Heizungsmathematik als API, lokal und deterministisch berechnet – die Output-, Rohr- und Durchflusszahlen, mit denen ein Installateur oder Heimwerker einen warmen Fußboden plant. Der Output-Endpunkt gibt die Wärme aus, die ein warmer Fußboden abgibt: etwa 2 BTU/h pro Quadratfuß für jedes °F, das die Bodenoberfläche wärmer als der Raum ist, also liefert ein 85 °F-Boden in einem 70 °F-Raum etwa 30 BTU/h/ft² – etwa 9.000 BTU/h über 300 ft², die Komfortgrenze, da der Boden bei ~85 °F gehalten wird. Der Rohr-Endpunkt gibt das Rohr und die Schleifen für eine Fläche bei einem Abstand an: Feldrohr = Fläche × 12 ÷ Abstand, also benötigt 300 ft² bei 9-Zoll-Abstand 400 Fuß Rohr, aufgeteilt in Schleifen unter ~300 Fuß (zwei 200-Fuß-Schleifen), damit die Pumpe sie durchdrücken kann. Der Durchfluss-Endpunkt gibt die Schleifendurchflussrate für eine Heizlast an, GPM = Last ÷ (500 × ΔT), wobei 500 die Wasserkonstante und ΔT die Vorlauf-Rücklauf-Differenz ist – 9.000 BTU/h bei einer ΔT von 20 °F benötigt 0,9 GPM. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Fußbodenheizungs- und Sanitäranwendungen, Hydronic-Design- und PEX-Layout-Tools, HVAC-Rechner für Auftragnehmer und DIY-Bau-Seiten. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Live, nichts gespeichert. 3 Compute-Endpunkte. Schätzungen – mit einer vollständigen Wärmeverlustberechnung überprüfen. Für die Gebäudelast eine HVAC-API verwenden; für die Rohrgeschwindigkeit eine Durchflussraten-API.
api.oanor.com/radiant-api
Pool Heating API
Swimming-pool and spa heating maths as an API, computed locally and deterministically — the thermodynamics a pool owner, builder or service tech sizes a heater and budgets a heat-up with. The heat-time endpoint gives the hours to warm a body of water: energy = gallons × 8.34 lb/gal × the temperature rise in °F (that many BTU), divided by the heater's BTU/hr output — raising 20,000 gallons by 10 °F is 1,668,000 BTU, about 4.2 hours on a 400,000 BTU/hr gas heater before surface losses. The heater-size endpoint inverts it: the output you need to hit a temperature rise within a target time, so the same job in 24 hours wants only about 69,500 BTU/hr. The heat-pump endpoint gives a heat pump's electricity and cost — kWh = thermal BTU ÷ 3412 ÷ the COP (5–6 for pool units in mild weather) — so that 1,668,000 BTU costs about 89 kWh at a COP of 5.5, a fraction of resistance heat. Pass the temperature rise directly, or a current and target temperature. Everything is computed locally and deterministically, so it is instant and private. Ideal for pool-builder and service apps, heater-sizing and quote tools, spa and hot-tub calculators, and energy-comparison sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Ideal figures — add for surface and wind losses. For pool chemistry use a pool-chemistry API.
api.oanor.com/poolheat-api
Degree Day API
Heating and cooling degree-day maths as an API, computed locally and deterministically. The daily endpoint computes the heating degree days, HDD = max(0, base − mean), and the cooling degree days, CDD = max(0, mean − base), for a single day from a base temperature and the daily mean — or the minimum and maximum, since the mean is taken as their average. The period endpoint sums the degree days over a list of daily temperatures (means or min/max pairs), returning the total HDD and CDD, the count of heating and cooling days and the average temperature — the standard way to characterise a heating or cooling season. The energy endpoint turns degree days into an energy estimate: the heat delivered is UA·DD·24/1000 kWh from the building heat-loss coefficient, the fuel or electricity input is that divided by the boiler efficiency (or a heat-pump COP), and — with an energy price — the cost. Everything is computed locally and deterministically, so it is instant and private. Ideal for building-energy, HVAC and facilities tools, heating-bill and fuel-budget estimation, weather-normalisation and energy-benchmarking apps, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is degree-day demand estimation; for U-value and heat-loss fabric calculations use a U-value API.
api.oanor.com/degreeday-api
API de calculadora de BTU para HVAC
Matemáticas de dimensionamiento de HVAC como API, calculadas local y determinísticamente a partir de factores estándar de regla general. El endpoint de refrigeración estima la carga del aire acondicionado para una habitación — en BTU por hora, toneladas de refrigeración y kilovatios — a partir del área del piso (en pies cuadrados o metros, o largo × ancho) usando una línea base de aproximadamente 20 BTU/h por pie cuadrado, con ajustes por el número de ocupantes, una cocina, exposición solar y altura del techo. El endpoint de calefacción estima la carga de calefacción a partir del área y una zona climática (templada a muy fría) o un BTU personalizado por pie cuadrado. El endpoint de conversión convierte entre BTU por hora, toneladas de refrigeración, kilovatios y vatios (una tonelada = 12,000 BTU/h ≈ 3.517 kW). Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Estas son estimaciones de regla general al estilo EnergyStar — se recomienda un cálculo de carga Manual J adecuado que tenga en cuenta el aislamiento, las ventanas y el clima local para una instalación real. Ideal para herramientas de HVAC y mejoras del hogar, guías de dimensionamiento de aires acondicionados y calefactores, aplicaciones de hogar inteligente y energía, y cotizaciones para contratistas. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 3 endpoints. Esto es dimensionamiento de HVAC; para el costo de funcionamiento de electrodomésticos, use una API de costo de energía.
api.oanor.com/hvac-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Wood Pellet API?
Qual è il limite di velocità di Wood Pellet API?
Quanto costa Wood Pellet API?
Posso cancellare l'abbonamento in qualsiasi momento?
Wood Pellet API è conforme al GDPR?
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/pellet-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/pellet-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/pellet-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/pellet-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
·
-
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.