🔏
API Docs
  • Beam API Docs
  • Overview
    • About Beam
    • API Requirements
    • Roles and Permissions
  • Getting Started
    • Requesting an Account
    • Using RESTful Tools
    • Webhooks
  • The Basics
    • Entities
    • Best Practices
    • Testing Accounts
  • OAuth
    • Overview
    • How to Authorize Access
      • Step 1: Generate Authorization URL
      • Step 2: Handle Authorization Response
      • Step 3: Request an Access Token
      • Step 4: Call API Endpoints
      • Step 5: Refresh the Tokens
  • API Endpoints
    • Overview
    • Get User Devices
    • Toggle Door
    • Invite User (internal)
    • Get Toggle History
    • Get User Info
    • Get User Settings
Powered by GitBook
On this page
  1. Overview

About Beam

PreviousBeam API DocsNextAPI Requirements

Last updated 4 years ago

Beam is a hardware-as-a-service product which enables garage doors of many makes and models to be controlled and monitored remotely. At the heart of it all is the Beam Controller (pictured below).

A Beam Controller physically connects to an account owner‘s garage door opener. It also connects to the internet via WiFi to communicate with the Beam Service. The following is representative of the overall architecture of Beam. You will notice that the Blackbox cannot be controlled locally, either via direct WiFi or Bluetooth.

Important: For security purposes, commands cannot be sent directly to a Beam Controller. All requests must flow through the Beam service.