Utilities
Integuru generates a production-ready HTTP API for a utility provider portal, covering 2 actions for billing history retrieval and payment option discovery. Both actions carry full API documentation and let energy-tech teams access account data programmatically without browser automation.
Last reviewed: July 2026
Overview
Integuru's Utilities integration provides production-ready HTTP API access to a utility provider portal, covering 2 actions: billing_history and list_payment_options. Both actions carry full API documentation with richer reference available. Integuru connects via direct HTTP requests rather than browser automation, so calls complete in under 3 seconds with a 99.9%+ success rate.
No public API. Utility provider portals typically expose no developer API. Accessing billing history or payment options programmatically has historically required manual login sessions or brittle browser scripts. Integuru stabilizes access to these internal endpoints for production use.
Energy-tech teams and utility account management platforms use this integration to pull billing history and discover available payment methods for accounts without building or maintaining a browser automation layer. See the full integrations catalogue for other platform integrations.
Use Cases
Integuru's Utilities integration covers the two core data-access workflows available in the utility portal.
- Billing history retrieval: Call
billing_historywith no parameters to retrieve the billing history for the authenticated utility account. - Payment option discovery: Call
list_payment_optionsto retrieve available payment methods. Pass anaccount_idto scope the lookup to a specific account number, or omit it to use the default account for the authenticated session.
Setup Notes
Integuru's Utilities integration authenticates against https://coautilities.com/wps/wcm/connect/occ/coa/home. Integuru manages the portal login session automatically. You configure credentials once during setup; Integuru handles re-authentication from that point forward.
billing_history requires no parameters. list_payment_options accepts one optional parameter, account_id; when the authenticated session is associated with a single utility account, omitting it is sufficient. When the account has multiple utility accounts, pass the specific account number to ensure the correct account's payment options are returned.
Full API documentation for both actions is available via Integuru's richer docs.