Use Cases
How It Works
1
External system triggers registration
Your app, portal, or platform sends a registration event to the Wiacom API — including the user identity information and the target location.
2
Wiacom processes the identity
Wiacom creates or updates the user record, applies consent settings, and triggers the access workflow configured for that location.
3
Access provisioned
Depending on the location’s configuration, Wiacom provisions a WiFi Pass credential, a Key Access delivery, or a portal authorization — and optionally sends a confirmation to the user.
4
Events returned
Registration, access, and lifecycle events are returned via webhook or API response for your system to consume.
Integration Points
Access Features Available via API
All Wiacom access features are available to API-triggered registrations:- Portal — RADIUS session authorization issued on API registration
- WiFi Pass — unique personal passphrase provisioned on the controller and returned via API or email
- Key Access — shared passphrase returned via API response or delivered by email
- Passpoint Connect — profile delivery triggered on API registration
- Horizon — personal SSID provisioned and lifecycle managed via API or PMS event
Getting Started
API access requires a Wiacom account with API credentials configured. Contact the Wiacom team to receive your API key and endpoint documentation.Request API Access
Talk to the Wiacom team about API and platform integration

