​

Extra information

Connector package documentation: System documentation: Connector Package Documentation

​

Setting up HTTP Client Yotpo

​

Steps

1. In Alumio Dashboard, go to Clients > HTTPS Client. Create a new HTTP Client and select Yotpo HTTP Client as the prototype of the HTTP Client.
2. Fill in the Base URI, and Client Secret
3. Save.

​

Subscribing to Entities from Yotpo

​

Steps

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

​

General Concept

We follow Yotpo documentation on building this connector so you can easily use the connector based on Yotpo API Reference. Entity It’s the entity you want to subscribe from Yotpo. Please refer to the entities in Management APIs from the Yotpo API Reference page. Request Parameters These are the parameters you can provide to get the needed entity based on Yotpo API Reference. Please look at the example below on how to fill the Request Parameters field when Retrieve order by ID entity That’s why we need to define the yotpo_order_id 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 the Retrieve order by ID entity. /orders/123 Input Transformer Any transformers 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 Yotpo.

​

Publishing Entity to Yotpo

​

Steps

1. Go to Connections -> Outgoing, create a new outgoing configuration, and select Yotpo Publisher as the publisher.
2. Select the action that you want the publisher to do with the data.
3. Select the Yotpo entity you want the data to be published.
4. 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). Action Currently, we support Create (HTTP POST method), Patch (HTTP PATCH method), and Delete (HTTP DELETE method). Entity We support publishing to most Yotpo endpoints. Please refer to the entities in Management APIs from the Yotpo 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 Order. Please select “Create” as the action and “Create Order” as the entity of the publisher. You can put the payload you want to send to Yotpo into the payload property in the data. Here is an example of the Possible Response after Creation. Alumio will send an API request to Yotpo with URL /orders HTTP Client It’s the HTTP Client configuration or prototype you will use to access Yotpo.