Vend

Previously known as VendHQ, now LightSpeedHQ.

​

Extra information

System documentation: LightSpeedHQ API Reference

​

Connector package documentation

​

Table of Contents

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

​

1. Setting up HTTP Client LightSpeedHQ

1.1 Steps

1. In the Alumio Dashboard, go to Clients -> HTTP Clients. Create a new HTTP Client and select “LightSpeedHQ HTTP Client” as the HTTP Client.
2. Fill in the Base URI and Bearer Token. (For more information, see LightSpeedHQ Authentication Reference)
3. You can optionally enable logging of request to get the log of the authentication.
4. Save the HTTP Client for use.

​

2. Subscribing to Entities from LightSpeedHQ

2.1 Steps

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

2.2 General Concept We follow LightSpeedHQ documentation on building this connector, so you can easily use the connector based on LightSpeedHQ API Reference. HTTP Client The HTTP Client configuration you will use to access LightSpeedHQ. Entity The entity you want to subscribe to LightSpeedHQ. Please refer to the entities from LightSpeedHQ API Reference page. Request Parameters These are the parameters you can provide to get the needed entity based on the LightSpeedHQ API Reference . Please look at the example below on how to fill path field when subscribing “Get a single brand” entity. Based on the documentation, we can see that the end point require “brand_id” as a parameter. That is why we set the “brand_id” inside the path key in the Request Parameters. Alumio will then make a request to LightSpeedHQ with the URL /brands/123

• 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.

​

3. Publishing Entity to LightSpeedHQ

3.1 Steps

1. Go to Connections -> Outgoing, create a new outgoing configuration and select “LightSpeedHQ Publisher” as the publisher.
2. Select the Action that you want the publisher to perform with the data.
3. Select the LightSpeedHQ 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. Action Currently, we support Create (HTTP POST method), Update (HTTP PUT method) and Delete (HTTP DELETE method) on submitting data to LightSpeedHQ. Entity We support publishing to most LightSpeedHQ endpoints. Please refer to LightSpeedHQ API Reference page. For example, we want to add a new product. Please select “Create” as the Action and “Create brand” as the entity of the publisher. Based on the documentation, it requires a “BODY PARAMS”. That is why we set the “BODY PARAMS” inside the payload key in the data. Alumio will send an API request to LightSpeedHQ with URL /brands Another example is when we want to delete a product by id. Please select “Delete” as the Action and “Delete a serial number” as the entity of the publisher. Based on the documentation, we can see that the end point require “serialnumber_id” as a parameter. That is why we set the “serialnumber_id” inside the path key in the Request Parameters. Alumio will then make a request to LightSpeedHQ with the URL /serialnumbers/1506951202871443456

• 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 LightSpeedHQ.