Structure of Endpoints

The devices data is split up in multiple JSON structures. This serves on the one hand for clarity, on the other hand it allows different access rights for different kinds of data.

Furthermore, each JSON object contains a typename and a revision. This can be used in order to identify the object and to know which set of attributes it should contain.

Elements to describe the used class.

Name	Description
Json+typeName	Name of the used class
Json+typeRevision	Revision of the used class: To ensure compability to old revisions, elements can only be newly added with a new revision.

Note

Since the type name and the revision have a "+" symbol in name, the URL for a direct access to them has to be encoded: The "+" symbol need to be replaced with "%2B".
example:
The URL
    [device_address]/api/v1/data/Json+typeName
has to be encoded into
    [device_address]/api/v1/data/Json%2BtypeName

List of endpoints/structures used by MKC devices:

• Hardware Information
• Network Configuration
• IO Configuration
• IO Data
• Access Keys
• HTTP Authentication