The REST + MQTT property flow, running. Work down the stages: each one shows the exact call it made, so you can copy it into your own client. Nothing is stored — tokens live in this tab only. Read the walkthrough.
Every URL below derives from one base domain. Use vion.swiss for production, or
your own domain for a self-hosted environment.
Derived endpoints
Authorization code with PKCE, in this tab. The redirect comes back to this page, so this page's URL must be a registered redirect URI on the client below.
The call this makes
Client credentials, straight from the page. The client's webOrigins must
include this page's origin, or the browser blocks the token request.
The call this makes
No prerequisites. Paste a token you already have — from the
curl on the walkthrough page, or from any client you can already sign in with.
A pasted token cannot be refreshed, so this mode stops working when it expires.
Token response
GET /Me returns your memberships and your identity provider user id. That id is
one half of both the subscriber id and the last will topic, so it is read here rather than
typed anywhere.
The call this makes
Four steps, in this order. The MQTT SUBSCRIBE has to be acknowledged before the REST call, because VION Cloud publishes each property's current value the moment it registers the subscription — and a push to a topic you are not listening on yet is lost.
The calls this makes