Reference · built on requestConnectorSensors, meters & gateways

Badger Meter BEACON

Meter reads, interval flow, consumption, and endpoint exceptions from BEACON Web Services for Badger Meter utilities.

Request accessPricing ↗

About

BEACON is Badger Meter's advanced metering analytics software for water utilities. BEACON Web Services expose it over REST at api.beaconama.net, or api.beaconama.ca for Canada. The Export Data Service returns billing reads, interval reads, flow, consumption, and exceptions from meters, encoders, and endpoints as CSV or JSON. The Data Exchange Import API takes CSV files that keep accounts, locations, meters, and reads in step with a billing or customer information system. Every export runs as a job you poll for a download URL.

Through Fibric an operator pulls the exports on a schedule inside the rate windows and proposes the import, the field visit, or the notice for your approval.

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

  • Latest billing reads through POST /v1/eds/read, with Billing_Read, Encoder_Read, Read_Method, Read_Time, Register_Number, and Tamper_Code columns
  • Interval reads and flow in a date range through POST /v1/eds/range at quarter_hourly, hourly, daily, or monthly resolution
  • Aggregate flow and reads through POST /v1/eds/flow and aggregated total consumption through POST /v1/eds/consumption
  • Alerts from meters, encoders, and endpoints through POST /v1/eds/exception_range, with Endpoint_SN, Register_Number, and exception dates
  • Endpoint health inside range exports: Battery_Level, Endpoint_Status, Signal Strength, and leak metrics
  • Export job state (queue, run, exception, done) and the reportUrl through GET /v1/eds/status/{edsUUID}
  • Import job state and its finished report through GET /v1/bde/import/{bdeUUID} and GET /v1/bde/import/{bdeUUID}/report

Proposed actions

  • Target capability: propose an account, location, meter, or read sync by posting a CSV to POST /v1/bde/import as a dry run
  • Target capability: propose accepting a dry run through PUT /v1/bde/import/{bdeUUID} after you have reviewed its report

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

What you can build

  • Send someone to the leak the endpoint flagged

    Pull exception_range exports each day and match leak metrics and endpoint alerts to a service point. Propose the field visit with the meter, register, and the date the alert began.

    With Leak Response

  • Reconcile consumption to what was billed

    Export monthly consumption per meter and compare it with the charge in the billing system. Propose the corrected chargeback lines, each meter's reads attached, before the invoice goes out.

    With Utility Chargeback, Bill Reconcile

  • Notice the meter that stopped reading

    Range exports carry Endpoint_Status, Battery_Level, and Signal Strength. When reads stop advancing or a battery runs low, propose the endpoint check with the last good read.

    With Submeter Drift, Data Freshness

Requirements

  • A BEACON utility account with web services enabled and a dedicated BEACON user for the integration
  • Export filters such as meterId, district, route, servicePointCycle, site, or meterSize, with startDate and endDate in ISO 8601
  • Import files as CSV, UTF-8, 70MB or less, with at least one of Account_ID, Meter_ID, or Location_ID
  • Requests sent as application/x-www-form-urlencoded; output chosen as csv or json with a csvSeparator of , ; : | or ~
Authentication
HTTP basic access authentication with a BEACON user name and password; Badger Meter recommends a unique email account and BEACON user created only for web services.

Limits

  • Sliding-window rate limits: 6 calls every 60 seconds, 24 every 60 minutes, and 48 every 24 hours, then HTTP 429 Too Many Requests
  • Exports are asynchronous: a POST returns 202 Accepted with an edsUUID, and the file exists only once the state is done
  • Pages default to 25,000 meters for flow and consumption and 10,000 for range, read, and exception_range; lastMeterID continues a page
  • Export Data Service v2 is a preview; this listing is written against v1

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 Badger Meter BEACON ↗

Questions and answers

Does BEACON push data, or must it be polled?
Polled. Each Export Data Service request returns 202 Accepted with an edsUUID and a statusUrl. You poll GET /v1/eds/status/{edsUUID} until the state is done, then fetch the reportUrl. The documentation lists no webhook or push channel.
How many calls can be made in a day?
48 every 24 hours under the published sliding windows, with 6 every 60 seconds and 24 every 60 minutes. Past the limit BEACON returns HTTP 429 Too Many Requests. Fibric schedules exports so that status polling fits inside these windows.
Can Fibric write reads or accounts into BEACON?
Only through the Data Exchange Import API, and only as a proposal. A CSV goes to POST /v1/bde/import, which runs a dry run by default. You review the report, then approve the PUT /v1/bde/import/{bdeUUID} that accepts it. Files must be 70MB or less.
Ask about Badger Meter BEACON

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 Badger Meter BEACON 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