Green Stack Docs
Green Stack Docs
  • Welcome
  • Fundamentals
    • Getting Started
    • Framework Architecture
    • Planning Your Solution
    • Using the Console
    • Requesting Support
  • Configuration
    • Digital Twin
    • Connectivity
      • Edge Devices
      • BACnet
    • Users & Access Control
    • Global Settings
    • Subscriptions & Billing
    • Personalization
  • Operations
    • Building Engineering
      • History Collectors
    • Reporting & Trending
      • Build & Run Reports
      • Report Groups
      • Scheduled Reports
    • Scheduler
    • Energy Manager
    • System Activity Log
  • Integration
    • Web Hooks
    • REST API
      • Making Requests
      • Responses and Errors
      • Versioning
      • Appendices
        • Building Type Codes
        • BACnet Object Types
        • Point Unit Codes
  • Open Source Credits
  • Glossary
  • Legal
Powered by GitBook
LogoLogo

©2019 - 2024 Counterbalance Software LLC

On this page
  • What are hooks?
  • Outbound Hooks
  • Inbound Hooks

Was this helpful?

  1. Integration

Web Hooks

What are hooks?

Hooks are inbound and outbound HTTP requests that allow you to integrate Green Stack with other systems.

Outbound Hooks

An Outbound Hook is an HTTP request initiated from Green Stack to remote system. Outbound hooks can be configured as a GET, PUT, or POST method. For PUT and POST methods, you may also configure a static or dynamic request body that can be included with the request.

Inbound Hooks

An Inbound Hook is an HTTP request sent to Green Stack from a remote system. An inbound hook can be configured as a trigger for an Algorithm and can be used to posture equipment in response to an external event, such as demand response, alarms, etc.

Last updated 1 year ago

Was this helpful?