Thingsee can be integrated with any custom cloud endpoint, but this is a specific case-by-case scenario. Additionally, please note that this customization will incur extra costs. We require information on how to establish the connection and authorize the API.
What can be customised
- protocol, what is the communication protocol and the URL to your cloud service; e.g. HTTP, MQTT, AMQP, CoAP, FTP..
- authorization, what are the credentials, apikeys, tokens, usernames that we need to use when authenticating to your cloud service.
- message format, are there some specifics that we need to change in the Thingsee Message payload data. e.g. add some specific field to be added, or a need to construct messaging topic including serial, etc.
Note that changing message format is something that takes time, and leads to a custom cloud extension and maintenance. Therefore we strongly prefer using of Thingsee Message format unless there are some mandatory changes that the system requires.