Custom Integration

Create custom integrations with any cloud endpoint

Thingsee can be integrated with any custom cloud endpoint. This option provides maximum flexibility for specialized requirements.

Note

Custom integrations are case-by-case configurations that may incur additional costs. Contact Haltian to discuss your requirements.

Customization Options

Protocol

Choose your communication protocol:

Protocol	Description
HTTP/HTTPS	RESTful API calls
MQTT	Publish/subscribe messaging
AMQP	Advanced message queuing
CoAP	Constrained application protocol
WebSocket	Real-time bidirectional
FTP/SFTP	File-based transfer

Authorization

Supported authentication methods:

Method	Description
API Key	Header or query parameter
OAuth 2.0	Token-based authentication
Basic Auth	Username/password
Certificate	mTLS client certificates
Custom	Proprietary authentication

Message Format

While Thingsee Message format is strongly recommended, customizations are possible:

Customization	Example
Additional fields	Add custom metadata to each message
Field renaming	Map Thingsee properties to your schema
Topic construction	Include serial number in MQTT topic
Envelope wrapping	Wrap messages in custom structure

Important

Changing message format creates a custom cloud extension requiring ongoing maintenance. We strongly recommend using standard Thingsee Message format unless absolutely necessary.

Setup Process

1. Define Requirements

Document your integration needs:

Endpoint URL and protocol
Authentication mechanism
Required headers or parameters
Any message format changes
Expected message volume

2. Contact Haltian

Provide your requirements to Haltian technical team:

Integration specification document
Test endpoint (if available)
Timeline requirements

3. Implementation

Haltian will:

Configure data routing
Implement authentication
Apply any message transformations
Test with sample data

4. Validation

Verify the integration:

Check data delivery
Validate message format
Test error handling
Confirm authentication

5. Production

Once validated:

Enable production data flow
Monitor initial traffic
Confirm stable operation

Example Configurations

HTTP REST API

protocol: HTTPS
method: POST
url: https://api.example.com/v1/iot/data
headers:
  Authorization: Bearer ${TOKEN}
  Content-Type: application/json
  X-Custom-Header: value
body: thingsee-message-array

MQTT Custom Topic

protocol: MQTT
broker: mqtts://mqtt.example.com:8883
authentication: certificate
topic_template: iot/${deploymentGroup}/${tsmTuid}/data
qos: 1

Custom Payload

message_transform:
  add_fields:
    customer_id: "CUST001"
    source: "thingsee"
  rename_fields:
    tsmTuid: device_id
    tsmTs: timestamp
    temp: temperature

Maintenance

Custom integrations require:

Aspect	Responsibility
Endpoint availability	Customer
Authentication	Customer
Data processing	Customer
Message routing	Haltian
Format transformation	Haltian
Error handling	Shared

Cost Considerations

Custom integrations may incur costs for:

Initial setup and configuration
Message format transformations
Ongoing maintenance
Support for custom features

Contact your Haltian account manager for pricing details.

Standard Alternatives

Before requesting custom integration, consider standard options:

Your Requirement	Standard Option
Real-time data	MQTT Data Stream
HTTP delivery	Azure IoT Hub, API Gateway
Custom processing	Standard format + your middleware
Data transformation	Process after delivery

Standard integrations are included in Thingsee subscription and require no additional development.