About the Reloadify category

[o.plokha]

Put topics about this connector package here.
Always check the ‘How to use the Alumio connector packages’ topic.

Extra information

System documentation: Reloadify API Reference

Connector package documentation

​​Table of Contents

• 1. Setting up HTTP Client Reloadify
  • 1.1 Steps
• 2. Subscribing to entities from Reloadify
  • 2.1 Steps
  • 2.2 General concept
• 3. Publishing entity to Reloadify
  • 3.1 Steps
  • 3.2 General concept

1. Setting up HTTP Client Reloadify

1.1 Steps

1. In the Alumio Dashboard, go to Clients → HTTP Clients. Create a new HTTP Client.
2. Select Reloadify HTTP Client as PlatForm and click next step
3. Fill in the Base URI, Token URI, Client ID and Client Secret.
4. Click on “Grant access to Reloadify” and key will be generated.
5. You can optionally enable logging of request to get the log of the authentication.
6. Click next step, fill the name of the HTTP Client and finally you can save the HTTP Client for use.

2. Subscribing to Entities from Reloadify

2.1 Steps

1. Go to Connections → Incoming and create a new incoming configuration and select “Reloadify Subscriber” as the subscriber.
2. Select the entity you want to subscribe to from Reloadify.
3. Add any request parameters needed to subscribe to the entity.
4. Select the Reloadify HTTP Client to use.
5. You can optionally add a transformer to transform the request parameters into something you will request from Reloadify.
6. You can also optionally enable pagination to allow Alumio fetches paginated entities.

2.2 General Concept

We follow Reloadify documentation on building this connector, so you can easily use the connector based on Reloadify API Reference.

Entity

The entity you want to subscribe to Reloadify. Please refer to the entities from Reloadify API Reference page.

Request Parameters

These are the parameters you can provide to get the needed entity based on the Reloadify API Reference .

Please look at the example below on how to fill path field when subscribing “Products - Return a list of products for a language” entity.

From the end point, we can see that we need to set “language_id” as parameters. That is why we set the “id” inside the path key in the Request Parameters.
We can also fill the query in JSON that will be translated by Alumio into Query Parameters in the query key in the Request Parameters.

Alumio will then make a request to Reloadify with the URL /v2/languages/Nederlands/products?page=1&per_page=0

• Path is the path parameter of the url. For example the {id}.
• Query is defined set of parameters attached to the end of a url.
  Example: www.url.com?type=true&start=0

HTTP Client

The HTTP Client configuration you will use to access Reloadify.

3. Publishing Entity to Reloadify

3.1 Steps

1. Go to Connections → Outgoing, create a new outgoing configuration and select “Reloadify Publisher” as the publisher.
2. Select the Method that you want the publisher to perform with the data.
3. Select the Reloadify entity you want the data to be published to.
4. You can optionally add any query data to the request on the key query.
5. You can optionally add any payload data to the request on the key payload.
6. Select the HTTP Client to use.

3.2 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 HTTP Put method and HTTP Delete method on submitting data to Reloadify.

Entity

We support publishing to most Reloadify endpoints.
Please refer to Reloadify API Reference page.

For example, we want to create a brand. Please select “Put” as the Method and “Brands - Create or update a brand for a language” as the entity of the publisher.

From the end point, we can see that we need to set “language_id” as parameters. That is why we set the “language_id” inside the path key in the data.
Based on the documentation, it requires a request body. That is why we set the request body in the payload key inside Alumio data.

Alumio will send an API request to Reloadify with URL /v2/languages/Nederlands/brands

• Path is the path parameter of the url. For example the {id}.
• Query is defined set of parameters attached to the end of a url.
  Example: www.url.com?type=true&start=0
• Payload is the data contained within a request.

HTTP Client

The HTTP Client configuration you will use to access Reloadify.