With the launch of Streams still fresh in our minds, we thought it might be helpful to provide a walkthrough of what is actually happening on the sending side of the stream and how it ultimately lands inside of Tandem. Tell us what you think!
You can also find out more about IoT integrations and APIs HERE.
Could anyone please explain how to rewrite the endpoint URL on Disruptive in some further detail? I've watched this portion of the video about 50 times in a row and cannot at all understand where the end of the text has been pasted from?
Hello @l.bell5H8JW!
The link comes for the connection itself. For example, I created a sample connection and then you can click the copy link icon to the right of the connection name.
If you paste it into a text editor it would look like this...
The last bit (AQAAAGqfCQrCFU91qY70OrVGKT4AAAAA) is unique to the specific connection. In that way you can send a specific call to each connection.
Near the end of the video I demonstrate how to create a field in the Disruptive Technologies interface that has the unique connection string (tandemId). Then the URL endpoint needs the "webhooks/generic?idpath=labels.tandemId" ammended to the end of the string. The tandemId is the variable that I created in Disruptive.
Hope that helps.
Can't find what you're looking for? Ask the community or share your knowledge.