### VBML Multiple Components with Styling Source: https://docs.vestaboard.com/docs/vbml VBML example using multiple components, each with specified height and width, allowing for distinct styling and layout on the Vestaboard. ```JSON { "props":{ "hours":"{36}{33}", "minutes":"{29}{31}", "quote":"The world is too much with us", "author":"William Wordsworth" }, "components":[ { "style":{ "justify":"center", "align":"center", "height":4, "width":22 }, "template":"{{quote}}" }, { "style":{ "justify":"center", "align":"center", "height":2, "width":22 }, "template":"{{author}}" } ] } ``` -------------------------------- ### Vestaboard Subscription API Introduction Source: https://docs.vestaboard.com/docs/subscription-api/introduction Provides an overview of the Vestaboard Subscription API, highlighting its capability to send messages to multiple Vestaboard subscriptions simultaneously. It also includes a note about deprecated V1 documentation and a warning regarding the security of JavaScript code examples and credentials. ```APIDOC Subscription API: Purpose: Send messages to multiple Vestaboard subscriptions at once. Note: Deprecated V1 docs are available separately. Security: Keep credentials safe. JavaScript examples are not for direct HTML embedding. ``` -------------------------------- ### Vestaboard Local API Enablement Response Source: https://docs.vestaboard.com/docs/local-api/authentication This is an example of the JSON response received after successfully enabling the Vestaboard Local API. It includes a confirmation message and the generated API key. ```json { "message":"Local API enabled", "apiKey":"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" } ``` -------------------------------- ### Vestaboard Local API Introduction Source: https://docs.vestaboard.com/docs/local-api/introduction This section introduces the Vestaboard Local API, explaining its purpose for local network interaction and potential decoupling from cloud services. It highlights prerequisites such as the Vestaboard being paired and online, the requirement for an IPv4 address for consistent results, and a note about JavaScript examples not being intended for direct HTML script tags. Future firmware updates may necessitate cloud connectivity. ```APIDOC Local API Introduction: Purpose: Enables parallel or decoupled interaction with Vestaboard on a local network. Prerequisites: - Vestaboard must be paired and online. - IPv4 address required for consistent results (IPv6 may cause inconsistencies). Notes: - JavaScript examples are not for direct use in HTML