We're beyond thrilled to announce a feature that we believe will redefine the way businesses interact with events happening in real-time. Say hello to Firehose! 🔥💧

In its simplest form, Firehose is an event-driven powerhouse that allows you to subscribe and receive events when something interesting takes place within your organization.

Getting started with Firehose is straightforward:

Below is a JSON sample that gives an idea of a typical Firehose event.

The event showcased above indicates that a user has entered a specific zone within a space, and your business has opted to track such occurrences.

Full documentation for configuring webhooks to capture specified types of firehose events and event schema are now available from the Developer Portal at Firehose Events.

: Plug-in developers have the ability to determine whether attendees have their microphones muted or not. This can be achieved through the use of the new function (documented here). In addition, a new mute state change hook allows you to register a callback to know when the user has changed the mute state. These additions allow developers to create more interactive and dynamic plugins, providing users with a better understanding of their audio status within the virtual environment.

: Resolved an issue related to the deletion of parent objects using Previously, using this function to delete a parent object would inadvertently lead to the deletion of child objects as well. With this fix, the function works as intended, ensuring that only the specified parent object is removed without affecting child objects.

: Fixed a problem where the 'move to' interaction feature did not function correctly when the target object was a child within a group. With this issue resolved, the 'move to' interaction now operates as expected even when dealing with grouped objects. This fix ensures a consistent and reliable interaction experience, allowing users to seamlessly interact with both grouped and ungrouped objects using the 'move to' functionality.

Please go check it out now in Vatom Spaces!

-Vatom Product Team

Developers building plugins for Vatom Spaces now have access to additional hooks for controlling media playback. The Hooks documentation for Plugins in Spaces has been expanded to cover these new features.

When a user logs in to use Vatom on a new device or after having been logged out, they will be presented with a sequence of pages known as a "login flow". This flow begins with a page asking for the user to identify themselves via SSO, email, or mobile phone number. They may then receive a "magic code" via one of these channels and be asked to confirm it on the next page of the flow, etc.

When developers invite users directly to their organization's own properties built with Vatom tech, they can customize the login flow itself. Examples include logging into a white-labelled wallet, micro-site built with Experience Kit, or app built with one of Vatom's other SDK's.

Instructions for customizing the login flow are now available at https://developer.vatom.com/wallet/login-page/overview.

The Vatom Loyalty Program allows each business to define its own currency and issue tokens in this denomination. When users collect and hold these tokens in their wallets, a separate balance will be maintained for each currency issued by a business participating in the Vatom Loyalty Program.

The Vatom REST API now provided nine new endpoints for managing and transacting tokens of the Loyalty Program currencies. For details see Vatom's Loyalty Program REST API documentation.

The Vatom REST API now covers , a query language that can be used to implement complex Allow Lists and lots more. It gives developers a way to execute a broad range of logic based on the information in wallets.

For details see Vatom's Allowl Language and REST API

Developer documentation has been updated to include more sample code along with recently added hooks and methods for developing plugins in Vatom Spaces. The Plugin API Reference now covers new hooks and methods available in Vatom Spaces v1.8.448.

This week, we've added new tabs to the top level structure of the developer documentation. This change sets us up to dramatically increase the number of topics that our documentation will cover.

In particular, we've broken out content previously stored under the "Documentation" tab and replaced that tab with three new tabs: "General", "Spaces", and "Smart NFT". More top level tabs will be introduced in the coming weeks.

Documentation for the Vatom REST API has been added at developer.vatom.com. This API allows developers to programmatically integrate many of the platform's features into their own applications. API endpoint capabilities include: