How to Integrate TagoIO with a Generic HTTPS Endpoint

General Tutorials
22

@mateus.silva Seems to be working now, thanks for the follow-up.

23

Hello All!

Is possible to send XML content?

Thanks

24

Hello @celio.gushiken,

Just to clarify the Generic HTTP middleware does not support XML content** out-of-the-box. That integration expects JSON in the request body. If you send XML to the generic endpoint, it won’t be parsed correctly by TagoIO’s middleware since it’s designed to receive JSON payloads and map fields based on JSON key names.

Recommended approach:

  • Convert the XML to JSON before sending it to the TagoIO Generic HTTPS Endpoint (e.g., using a proxy or webhook transformer).
  • Alternatively, build a custom middleware or Analysis that accepts XML, converts it to JSON, and then pushes to the TagoIO APIs.
25

Update: batch uplinks are now supported

The /uplink endpoint now accepts an array of objects in the body, in addition to a single object. Each item is processed independently using the same Authorization and the same Additional Parameter rules, so there is nothing extra to configure.

Example:

[
  { "serial": "AA-BB-01", "payload": "0011AA", "port": 10 },
  { "serial": "AA-BB-02", "payload": "0022BB", "port": 10 }
]

A few notes:

  • Every item must resolve a serial. If any item is missing it, the whole request fails with 400.
  • Items can target different devices. Device lookups are cached within the request, so duplicate serials in the same batch do not cost extra.
  • All items in one request share the same group, so they stay correlated when stored in TagoIO.

The guide above has been updated with a new section under step 3.