Legacy BCL API

The new implementation of the BCL maintains support for the legacy BCL API v2.0, identified by appending &api_version=2.0 to the URL query.

Search Endpoint

The main syntax for querying is as follows:



KEYWORD—is the term to search on, such as "window" or "boiler". To do a wildcard search, use the "*" symbol.

FORMAT—is the return format wanted. XML and JSON are both supported; if no format is specified, JSON will be returned.

FILTER_NAME & FILTER_VALUE—are used to narrow down the search results. Multiple name-value pairs can be specified.

api_version=2.0— is appended to the end of the URL request to ensure backward compatibility. The legacy syntax will not work without specifying this api_version.

Read on for more details on filters and query parameters that can be used in search requests, or view the examples section for ready-to-use examples.


Below is a list of common filters that can be used to narrow down search results:

Filter NameDescription
bundleType of content. The possible values for this filter are: nrel_measure and nrel_component
name or labelName of the component or measure
ss_field_display_nameDisplay Name of the component or measure
ss_uuidUUID of the component or measure
ss_vuuidUnique Version ID of the component or measure
ss_descriptionContent Description
ss_modeler_descriptionModeler Description for the component or measure
ss_field_version_modifiedVersion Modified date value from the component or measure's XML file
sm_vid_measure_tagsClassification tag of the measure. See Measure Tags for a complete tag list and the examples below for query syntax.
sm_vid_component_tagsClassification tag of the component. See the Component Tags page for a complete list and the examples below for query syntax.
tidTaxonomy ID of the measure tag or component tag. See Component Tags for a complete list of tags and their respective taxonomy ID and the examples below for query syntax.
ss_field_class_nameOpenStudio Classname of the component or measure
ss_source_manufacturerManufacturer of the item represented by the component
ss_source_modelModel number of the item represented by the component
ss_source_serial_numberSerial number of the item represented by the component
ss_source_yearYear of manufacture of the item represented by the component
ss_source_urlSource URL of the item represented by the component


Content attributes can also be used to filter search results. Attributes are stored as a name and value pair. For example:

{ "name": "Measure Type", "value": "ModelMeasure"}

To query by attribute, specify the legacy attribute name and its desired value. The list of legacy attribute names can be found on the Attributes page.


Query Parameters

In addition to filters, several query parameters are also available to narrow down the search results. These query parameters are appended to the search URL but do not need the 'fq=' syntax which indicates filters.

For example, the following URL can be used to paginate the search results to 10 per request and return page 2 of the results:


The list of query parameters can be found in the table below.

Query Parameter NameDescription
show_rowsNumber of results to return on each page. Default is 50.
pageThe page to return. This is 0-based (the first page is page=0).
api_versionUsed to specify the legacy API. Set api_version=2.0 to use the legacy syntax.

Geospatial Search

Geospatial searching is enabled for content with Latitude and Longitude attributes. This search currently exists for Location-Dependent Components such as Weather Files and Design Days, but is possible on any component or measure content provided that Latitude and Longitude are both provided as attributes in the component.xml or measure.xml file.

To perform a geospatial search, the special location: prefix is used in the keyword section of the search query URL. There are three syntaxes available for this query type, as described below.

TypeKeyword Syntax
Latitude and Longitudelocation:{latitude},{longitude}
City and Statelocation:{city},{state abbreviation}

See below for geospatial search examples.

Download Endpoint

Measures and Components can be downloaded via the BCL API. Individual or multiple content can be downloaded in the same request, by specifying a single uuid or a list of uuids. For individual requests, the version of the content can be specified. You will need the uuid

The basic syntax for downloading is as follows:



UUID—is either a single uuid or a list of uuids.

See below for downloading examples.

Taxonomy Endpoint

The taxonomy endpoint is used to programmatically return the Measure Tags or Component Tags hierarchies. This can be useful for user interface development.

The response can be returned in either XML or JSON format. To return all Measure Tags:


To return all Component Tags:


Metasearch Endpoint

The metasearch endpoint can be used to retrieve the statistics of a search—such as number of results overall as well as the number of results per filter relevant to the search. This endpoint can be useful for user interface development.

Basic syntax is the same as the search endpoint; for example:


This query will return the total number of results overall and the number of results per measure tag or taxonomy ID (tid), for example.


Expand the sections below to view API usage examples.

Download the latest version of a single measure or component:


Download multiple measures or components (measures and components can be downloaded at the same time):