Reference · built on requestConnectorBuilding management platforms

75F

Sites, zones, equipment points, and histories from 75F through its Haystack API at api.75f.io, with writes to writable points.

Request accessPricing ↗

About

75F is an IoT building automation system: a Central Control Unit per site with wireless sensors, HyperStat and SmartNode devices, and the Facilisight portal. Its external API is a Haystack-style REST interface at api.75f.io, fronted by an Azure API Management developer portal. Products such as Readonly and Readwrite carry a subscription key, and a bearer token comes from POST /oauth/token with client credentials. Ops include read by filter or id, hisReadMany for histories, pointWrite to writable points, and hisWriteMany.

Through Fibric, an operator reads zone temperatures, set points, and schedules from a 75F site and proposes a write to a writable point for your approval. The record shows what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from 75F 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

  • Site-level information, all zones for a site, and all points generated by equipment on a site
  • Entities filtered by Haystack tags through GET /ph/read, for example siteRef, vav, zone, current, and temp
  • Vacations and schedules configured for a site
  • Current value of a historized or writable point by id, with tags such as curVal, kind, unit, and tz
  • Point history over a date range through hisReadMany, with ranges like today, yesterday, or a date pair
  • The priority array returned by pointWrite: duration, level, val, and who per level

Proposed actions

  • Target capability: propose a pointWrite to a point tagged writable, at a chosen level and duration
  • Target capability: propose hisWriteMany of samples into historized points

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

What you can build

  • Fix a comfort complaint with a bounded override

    Read the zone's current temp and set point, confirm the target point is writable, and propose a pointWrite with a duration so the override lapses on its own.

    With Comfort Complaint, Setpoint Drift

  • Cut load at the peak

    Read zone set points and histories, pick zones with room to move, and propose a set of writes for the demand window.

    With Peak Demand, Event Response

  • Keep sensors honest

    Poll hisReadMany for temperature, humidity, and CO2 points, flag flat or missing series, and propose a check.

    With Sensor Health, Indoor Air

Requirements

  • A Facilisight account set up as Secondary Manager on every site you touch, using a standard username and password, not O365 or Gmail sign-in
  • A developer portal user with an approved subscription to a product such as Production Readonly or Readwrite
  • The API Management add-on in Facilisight, which holds Read, Write, and Special Schedule API keys and supports key rotation
  • Point ids or tag filters located in the Facilisight Site Explorer
Authentication
An Azure API Management subscription key in Ocp-Apim-Subscription-Key plus a bearer token from POST https://api.75f.io/oauth/token with grant_type=client_credentials, where the client id and secret are a Facilisight username and password.

Limits

  • Only points tagged writable can be written; relays, analog outputs, and direct physical components cannot
  • One physical change can take several point writes, such as a damper's config points for min and max
  • Bearer tokens expire (expires_in 3600 in the example) and client application credentials expire within 24 hours
  • Points the user lacks permission for return HTTP 200 with an empty grid, so gaps have to be checked

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 75F ↗

Questions and answers

What credentials does the 75F API need?
Two things on every call: an Ocp-Apim-Subscription-Key for a subscribed product, and an Authorization: Bearer token from POST https://api.75f.io/oauth/token with grant_type=client_credentials, where client_id is a Facilisight username and client_secret is its password.
Which points can be written?
Only points with the writable tag, which Site Explorer lists with a writable query. Relays, analog outputs, and physical components are not exposed. Some actions need several writes, such as a VAV damper's config points for min and max.
How is history read?
Through hisReadMany with ids prefixed @ and separated by commas, and a range: today, yesterday, a date, a date pair, or a date-time pair. The range includes the start and excludes the end, in the point's configured time zone.
Ask about 75F

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 75F 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