Reference · built on requestConnectorBuilding management platforms

Honeywell Forge for Buildings

Equipment, points, locations, and telemetry from Honeywell Forge for Buildings, modeled in Brick Schema. Read-only reference.

Request accessPricing ↗

About

Honeywell Forge for Buildings is Honeywell's cloud building performance platform, and its API exposes the building model and BMS telemetry to a customer's own applications. The Forge Data API is versioned in the URL, for example https://api.us.buildings.honeywell.com/data/v1/equipment, and is offered from US, EU, and UAE data centers. Every response is expressed in the Brick ontology by default.

Through Fibric, an operator searches equipment by Brick type such as brick:AHU, walks hasPoint and hasLocation relationships, pulls telemetry for a set of points and a time window, and produces the comparison or exception you asked for. This reference listing is read-only; it proposes no writes to the BMS.

This is a reference listing. It documents what Fibric would read from Honeywell Forge for Buildings and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Equipment by Brick type, label, or id through POST /data/v1/equipment with a q filter, include list, sort, and page block
  • Points and Locations through POST /data/v1/points and POST /data/v1/locations, or one record through GET /data/v1/{resourceName}/{id}
  • Telemetry for chosen point ids and a values.timeStamp range through POST /data/v1/telemetry, with optional date-histogram aggregations such as a 24h avg
  • Change-of-value telemetry only, by sending the covFlag header, with the timestamps in the response given in epoch nanoseconds
  • The last value of AssetTelemetry points through the last query operator on values.value
  • The customer's building model relationships such as hasPoint, hasLocation, and hasTimeseriesId

Proposed actions

Read-only. Actions need a separate connector.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Compare sites on the same yardstick

    Brick types make an AHU an AHU in every building. The operator pulls telemetry for the same point classes across sites, normalizes by location, and proposes the outliers worth a visit.

    With Site Benchmark

  • Find points that went quiet

    The last operator returns the final value per point. The operator flags points whose last timestamp is stale against their interval and proposes a sensor check with the gap shown.

    With Sensor Health

  • Reconcile meters against the main

    Telemetry aggregates by date histogram, for example a 24h avg per point. The operator totals sub-meters under a location, compares them with the main, and proposes which meter to inspect when the gap grows.

    With Submeter Drift

Requirements

  • An active subscription to RBM base connect or the Honeywell Forge for Buildings API SKU
  • A Portfolio Manager, Organization Manager, or Developer privilege to create API credentials
  • Customer modeling completed and published, with site telemetry flowing into Forge
  • The Region of the customer's deployment, US, EU, or UAE, to pick the data center host
  • An expiry date on each credential; Honeywell recommends short expiries and yearly rotation
Authentication
OAuth 2.0 client_credentials with a Client ID and Secret from API Credentials under Integrations in the Honeywell Forge for Buildings portal, exchanged for a Bearer JWT; an ApiKey header and a customerId header accompany data requests.

Limits

  • Rate limits by subscription: Trial 5, Standard 10, Core 15, and Enterprise 20 calls per minute, with 429 beyond that
  • Page size is at most 10,000 records and defaults to 25; above 50,000 total items you must use scroll paging
  • Telemetry volume per request depends on the number of points, days, and interval, and requests take epoch milliseconds while responses return nanoseconds
  • The published Data API is read-only; credentials mention an App ID for BMS point writes, but no write endpoint is in the public specification

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Honeywell Forge for Buildings ↗

Questions and answers

What does a search request look like?
A JSON body with q (operators eq, in, wi, exists, last, and, or, not), an include list of fields, sort, keywords, and a page block. Datetime fields accept epoch milliseconds or expressions such as now/d - 7. Set disableContext to true to drop the schema context from equipment, point, and location responses.
Which headers must every call carry?
An Authorization Bearer token from the OAuth 2.0 exchange, the ApiKey header, and the customerId header naming the customer whose data you request. Responses return X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset so you can pace calls.
How long do API versions last?
A major version is a breaking change and is published only after the prior major version is deprecated. Honeywell announces deprecation in release notes and keeps the deprecated API functional for a 6-month period. Minor and patch changes stay backward compatible.
Ask about Honeywell Forge for Buildings

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Honeywell Forge for Buildings through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy