Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
API Discover calls
The discover calls are used to learn about the present state of a given MobiusFlow instance
MobiusFlow Hub ID
{"value":"000001"}
MobiusFlow Service ID
{"value":"020"}
MobiusFlow Hub ID
{"value":"000001"}
MobiusFlow Service ID
{"value":"020"}
MobiusFlow Object Profile ID
{"value":"014A"}
MobiusFlow Hub ID
{"value":"000001"}
MobiusFlow Service ID
{"value":"020"}
MobiusFlow Object Profile ID
{"value":"014A"}
MobiusFlow Object Instance ID
{"value":"0001"}
MobiusFlow Hub ID
{"value":"000001"}
MobiusFlow Service ID
{"value":"020"}
MobiusFlow Object Profile ID
{"value":"014A"}
MobiusFlow Object Instance ID
{"value":"0001"}
MobiusFlow Resource ID
{"value":"40"}
API Service Calls
The service calls are used to read, add, remove and manipulate MobiusFlow services.
Description of MobiusFlow Engine RESTful API V1
The MobiusFlow Engine API is used interface with MobiusFlow via http and https. The API allows clients to perform all functions within MobiusFlow, from managing user accounts, to getting and setting data, as well as manipulating the MobiusFlow configuration by adding, removing and editing MobiusFlow objects, services and flows.
If connecting to a local instance of MobiusFlow, the http protocol can be used. If connecting to an instance of MobiusFlow via the internet, https should be used. The API is always exposed on port 8443.
All endpoints lead with:
{{protocol}}://{{hostname}}:8443/api/v1
Where the protocol and hostname parameters are replaced with the true protocol and hostname. For example, in the case of connecting to a local instance of MobiusFlow, the leading path would look like:
http://localhost:8443/api/v1
API Object & Resource Calls
The object calls are used to read, add, remove and manipulate MobiusFlow objects and resources.
API Authorization calls
The authorization controller is used to login to the API, in addition user management.
When a login call is completed, the API will return a bearer token which should be used in the auth header of all future calls. This token is set to expire 10 minutes after its generation.
A refresh token is also included in the login response, and this is used in the body of the refresh call to get new tokens with refreshed expiry times. Ensure a refresh call is made prior to any given bearer token's expiry to avoid having to login again.
API Calls for Node-RED Flows
Used get and set the full configuration the flows.
API Calls for Service Profiles, Object Profiles and Command Profiles
API Send Command Calls
Additionally, the API allows clients to subscribe to specific real-time events within happening within a given MobiusFlow instance (see ). In this use case, the API will upgrade the client to use the Websocket protocol (ws / wss).
All API endpoints are described in the following subsections. The subsections are divided into the functional groups (controllers); , , , , , , , and .
Swagger documentation describing the API in full, can be found . This documentation includes example bodies and responses for every endpoint. Finally, a postman collection containing parameterised examples of all client calls can be downloaded below.
API Subscription Websocket
Full functionality of Subscription Websocket is described in the connect call below.
API Calls for Licence Management
MobiusFlow Hub ID
{"value":"000001"}
MobiusFlow Service ID
{"value":"020"}