hvacapi.net

An API-first toolkit for HVAC — codes, brands and diagnostic recipes for the systems people actually install.

A reference on HVAC data and integration — the protocols, the catalogues and the directory structures that any HVAC API has to handle correctly.

hvacapi.net covers the data and integration side of HVAC — fault codes, control protocols, refrigerant catalogues and the certified-product directories that underwrite US procurement. The angle is the structured-data surface a developer or integrator works against, rather than the equipment itself or the trade techniques of installation.

Most HVAC data lives in formats that resist programmatic use — service manual PDFs, vendor portal lookups, register maps in datasheets. Yet the actual workflows that consume the data, from a technician on a rooftop unit checking a fault code to a building-automation contractor mapping BACnet objects, are inherently structured. The gap between the data form and the workflow form is exactly where APIs and catalogues earn their keep, and the operational vocabulary the API has to handle correctly is well-defined even when no individual product covers it end to end.

The glossary above sets out the load-bearing concepts — fault code, BACnet, Modbus, refrigerant blend, AHRI directory — that any HVAC data surface has to handle to be taken seriously by technicians and integrators. Each term carries an operational and a compliance weight in HVAC that does not translate cleanly from generic IoT contexts. Readers approaching this topic from a developer, integrator or distributor background will find the terms here line up with how manufacturers, controls vendors and the AHRI directory itself actually use them.

Key terms

Fault code

A short alphanumeric code displayed by HVAC equipment to indicate a specific detected fault or diagnostic state.

How Each manufacturer maintains a private mapping from internal sensor readings to fault codes, the controller displays the code on the unit or transmits it over a service bus, and technicians cross-reference the code in the service manual.

Why Fault codes are the single most-searched HVAC data type on the open web, which both demonstrates demand and justifies the existence of a code-resolution API.

BACnet

A building automation and control network standard widely deployed in commercial HVAC controls.

How Devices speak a common application-layer protocol across Ethernet, MS/TP or IP transports, object models describe sensors and setpoints, and a BACnet network can be composed across multiple vendors.

Why BACnet is the lingua franca of mid-to-large commercial HVAC controls, and any HVAC API that ignores it is unfit for any building bigger than a strip mall.

Modbus

A serial and TCP-based industrial protocol used in lighter-duty HVAC controls and equipment integration.

How A master polls registers on one or more slave devices, each register holds an integer value, and higher-level meaning is conveyed by a vendor-published register map rather than by a protocol-level object model.

Why Modbus is the price-floor protocol of HVAC integration and persists alongside BACnet, so an API serving real-world projects has to be Modbus-aware as well.

Refrigerant blend

A multi-component refrigerant whose composition is engineered to deliver specific thermodynamic and environmental characteristics.

How Components are blended at the factory to a defined mass fraction, the blend behaves as a near-azeotrope in the operating envelope, and service procedures require liquid-phase charging because vapour fractionates.

Why The global refrigerant transition under the Kigali Amendment is dominated by blends, and an HVAC catalogue API has to track blend properties accurately to remain useful through that transition.

AHRI directory

A public certified-product directory maintained by the Air-Conditioning, Heating and Refrigeration Institute for rated HVAC equipment.

How Manufacturers submit equipment for third-party-witnessed performance testing, results are published in a searchable directory keyed by AHRI reference number, and procurement documents reference the AHRI number as proof of rated performance.

Why AHRI numbers are the linchpin of US HVAC procurement compliance and are exactly the kind of structured data an API mirror should surface natively.

Frequently asked

What is hvacapi.net?

hvacapi.net is a topic surface for HVAC data and integration — the protocols, the catalogues and the directory structures that an HVAC API has to handle to serve real-world technician and integrator workflows.

What is an HVAC API in practical terms?

An HVAC API exposes structured data that technicians, integrators and software vendors currently have to scrape from PDFs and vendor portals — fault-code-to-description mappings, equipment specifications, refrigerant properties, AHRI certifications. The value of the API form is that it makes those lookups programmatic rather than manual, and the data stays current without each consumer scraping their own copy.

Which protocols matter for HVAC integrations?

BACnet dominates mid-to-large commercial HVAC controls, with BACnet/IP and BACnet MS/TP being the common transports. Modbus is the price-floor protocol for lighter-duty equipment and refuses to disappear because of its simplicity. Any serious HVAC integration project has to be literate in both, because real buildings are typically mixed.

How can I get in touch about hvacapi.net?

Email [email protected] for editorial corrections, topic suggestions or partnership ideas relating to HVAC data and APIs.

Get in touch

Editorial corrections, partnership ideas, or topic suggestions — write to [email protected] or use the form below.

Thanks — we’ll be in touch.