​

Extra information

System documentation: [Streak API Reference] Streak Connector Package Documentation

​

Setting up HTTP Client Streak

​

Steps

• In Alumio Dashboard, go to Clients > HTTPS Client. Create a new HTTP Client and select Streak HTTP Client as the prototype of the HTTP Client.
• Fill in the Base URI, and Username.
• Save the Client for use later.

​

Subscribing to Entities from Streak

​

Steps

• Go to Connections -> Incoming and create a new incoming configuration and select Streak Subscriber as the subscriber.
• Select the entity you want to subscribe from Streak .
• Add any request parameters needed to subscribe to the entity (optional).
• You can optionally add a transformer to transform the request parameters into something you need.
• Select the Streak HTTP Client to use.

​

General Concept

We follow Streak documentation on building this connector so you can easily use the connector based on Streak API Reference. Method It’s the Method you want to subscribe from Streak. Based on the Method, the Entity will change. Please refer to the entities in Management APIs from Streak API Reference page. Entity It’s the entity you want to subscribe from Streak . Please refer to the entities in Management APIs from Streak API Reference page. Request Parameters These are the parameters you can provide to get the needed entity based on Streak API Reference. Please look at the example below on how to fill the Request Parameters field when subscribing userKey. That’s why we need to define the userKey property inside the path property in the Request Parameters field. The properties inside query parameters will be parsed as query parameters. Here is the final URL that will be called when using such Request Parameters field on Get User. /api/v1/users/agx… Input Transformer Any transformer’s set here will be executed after the Request Parameters are loaded. So, you basically can add any transformer to provide and transform the request parameters into anything you need either as path parameters and/or as query parameters of an entity. HTTP Client It’s the HTTP Client configuration or prototype you will use to access Streak .

​

Publishing Entity to Streak

​

Steps

• Go to Connections -> Outgoing, create a new outgoing configuration, and select Streak Publisher as the publisher.
• Select the action that you want the publisher to do with the data.
• Select the Streak entity you want the data to be published.
• You can optionally add any query parameters to the request.
• You can also optionally add any transformers to transform the data into anything you need before submitting it to Streak .
• Select the HTTP Client to use.

​

General Concept

Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in outgoing configuration), though you can also add or modify payload using the Request Transformer. Method Currently, we support Post (HTTP POST method), Put (HTTP PUT method), and Delete (HTTP DELETE method). Content-Type and Request Encoder We Support publishing Streak endpoints with form-urlencoded format and json format, Make sure Content-Type for Header and Request Encoder is the same format. Entity We support publishing to most Streak endpoints. Please refer to the entities in Management APIs from the Streak API Reference page. Based on the documentation, some endpoints may need one or more path parameters. For endpoints that require an object as the request payload, please look at the example below. For example, we want to Create a stage. Please select “Put” as the action and “Create a stage” as the entity of the publisher. curl —request PUT
—url https://api.streak.com/api/v1/pipelines/pipelineKey/stages
—header ‘accept: application/json’
—header ‘content-type: application/x-www-form-urlencoded’
—data name=string You can put the payload you want to send to Streak into the payload property in the data, don’t forget that this endpoint use application/x-www-form-urlencoded, that’s why we set the Content-Type and Request Encoder to Form URL Encoded Alumio will send an API request to Streak with URL /api/v1/pipelines/……./stages HTTP Client It’s the HTTP Client configuration or prototype you will use to access Streak .