15.2. API Catalog Reference¶
This section is not intended to be read as a narrative description of system behavior, but to serve as a structured reference for developers implementing or integrating with the GEISA API.
It serves as a comprehensive catalog of all defined API calls, including:
MQTT topic structures
Required and optional parameters
Message payload formats
Expected responses
Error conditions, where applicable
GEISA APIs are implemented using MQTT topic hierarchies. Each API call is defined by:
The MQTT topic structure
The direction of message flow
The associated request and response payload definitions
References to relevant sections of the GEISA specification that define relevant behavior and constraints
Note
In the event of a conflict between this API catalog and the specific description in each API reference section, the API reference section SHALL prevail.
15.2.1. API Topic and Permission Catalog¶
Note
In the topic definitions below, <userid> refers to the platform-local
identifier of the requesting GEISA application instance (see Glossary).
Category |
Topic |
Role |
Action |
Direction |
Message Name |
Message Type |
|---|---|---|---|---|---|---|
|
Application |
Publish |
App → Platform |
|
Request |
|
|
Application |
Subscribe |
Platform → App |
|
Response |
|
|
Application |
Publish |
App → Platform |
|
Request |
|
|
Application |
Subscribe |
Platform → App |
|
Response |
|
|
Platform |
Wildcard Subscribe |
App → Platform |
|
Request |
|
|
Platform |
Publish |
Platform → App |
|
Response |
|
|
Platform |
Wildcard Subscribe |
App → Platform |
|
Request |
|
|
Platform |
Publish |
Platform → App |
|
Response |
|
|
Application |
Subscribe |
Platform → App |
|
Broadcast |
|
|
Application |
Subscribe |
Platform → App |
|
Directed |
|
|
Application |
Publish |
App → Platform |
|
Directed |
|
|
Platform |
Publish |
Platform → App |
|
Broadcast |
|
|
Platform |
Publish |
Platform → App |
|
Directed |
|
|
Platform |
Wildcard Subscribe |
App → Platform |
|
Directed |
|
|
Application |
Publish |
App → Platform |
|
Request |
|
|
Application |
Subscribe |
Platform → App |
|
Response |
|
|
Application |
Subscribe |
Platform → App |
|
Request |
|
|
Application |
Publish |
App → Platform |
|
Response |
|
|
Platform |
Wildcard Subscribe |
App → Platform |
|
Request |
|
|
Platform |
Publish |
Platform → App |
|
Response |
|
|
Platform |
Publish |
Platform → App |
|
Request |
|
|
Platform |
Wildcard Subscribe |
App → Platform |
|
Response |
|
|
Application |
Subscribe |
Platform → App |
|
Broadcast |
|
|
Platform |
Publish |
Platform → App |
|
Broadcast |
|
|
Application |
Publish |
App → Platform |
|
Request |
|
|
Application |
Subscribe |
Platform → App |
|
Response |
|
|
Platform |
Wildcard Subscribe |
App → Platform |
|
Request |
|
|
Platform |
Publish |
Platform → App |
|
Response |
|
|
Application |
Publish |
App → Platform |
|
Request |
|
|
Application |
Subscribe |
Platform → App |
|
Response |
|
|
Application |
Publish |
App → Platform |
|
Request |
|
|
Application |
Subscribe |
Platform → App |
|
Response |
|
|
Platform |
Wildcard Subscribe |
App → Platform |
|
Request |
|
|
Platform |
Publish |
Platform → App |
|
Response |
|
|
Platform |
Wildcard Subscribe |
App → Platform |
|
Request |
|
|
Platform |
Publish |
Platform → App |
|
Response |
|
|
Application |
Subscribe |
Platform → App |
|
Broadcast |
|
|
Application |
Publish |
App → Platform |
|
Request |
|
|
Application |
Subscribe |
Platform → App |
|
Response |
|
|
Platform |
Publish |
Platform → App |
|
Broadcast |
|
|
Platform |
Wildcard Subscribe |
App → Platform |
|
Request |
|
|
Platform |
Publish |
Platform → App |
|
Response |
Actuator payloads are defined by GeisaActuatorGet_Req,
GeisaActuatorGet_Rsp, GeisaActuatorSet_Req, and
GeisaActuatorSet_Rsp. Status and control are permission-gated.
Actuator support and target availability are platform-specific.