Covered in this article
Related pages
Lightspeed-ecom actions Lightspeed-ecom Technical Notes Lightspeed-ecom triggers
Latest Changelog
Version 1.0.2 ()
Lightspeed-ecom component

Lightspeed-ecom component

Lightspeed ECom API component for iPaaS platform.

Authentication

You should request API keys for your shop (api_key & api_secret) via ticket to support.

Authentication is managed via HTTP authentication. There are several clusters which your app can be installed on. During the installation you should get the cluster_id. Please make sure you specify API requests to the correct cluster URL.

Cluster URLs There are two clusters which your app can be installed on. During the installation we send you the cluster_id. Please make sure you send API requests to the correct cluster.

CLUSTERS

  • eu1: https://api.webshopapp.com/
  • us1: https://api.shoplightspeed.com/

Credentials

Lightspeed-ecom - Credentials

Environment URL

Url of the Lightspeed eCom cluster. Fro example,

  • for EU: api.webshopapp.com
  • for US: api.shoplightspeed.com

Environment language

Lightspeed eCom shop language.

Client ID

API Key which you received from support during configuration a shop.

Client Secret

API Secret which you received from support during configuration a shop.

Technical Notes

The technical notes page gives some technical details about Lightspeed-ecom component like changelog.

Triggers

Lightspeed-ecom component includes the following triggers:

  1. Polling entity
    This trigger polls for existing and updated objects where you can select object type.

  2. Webhook subscription
    This trigger can create webhook to receive any changes for chosen type of entities.

Actions

Lightspeed-ecom component includes the following actions:

  1. Create Object
    Action creates a new record/object. This action is supported by limited list of entities.

  2. Upsert Object
    Action creates a new object or updates object which already exists by provided ID. This action is supported by limited list of entities.

  3. Update Object
    Action updates object which already exists by provided ID. This action is supported by limited list of entities.

  4. Lookup Object By ID
    Action gets a list of objects by filters or specific object by provided ID.

  5. Delete Object By ID
    Action removes object which already exists by provided ID.

Additional info

Pagination

The component is providing request of a whole list of an entity by iterative API requests without user intervention.

A bit of theory:

Lightspeed eCom API limits the number of returned objects to 50 by default and 250 as max. When requesting large data sets it may be necessary to send multiple requests to retrieve all of the data. The meta-dictionary that’s returned tells the current page, and if there’s another page of results after this one, the next entry gives you the URL where it can be fetched. Depending on the structure of your data, it’s possible that the API may not be able to return the number of resources requested before a HTTP 504 (Gateway Timeout) happens. For example, if your first 100 orders have 1,000 line items each, you might hit a 429 when trying to fetch them. You can control the page size for a GET request with the limit parameter.

Coming back to the component:

In the component, at the Polling Trigger configuration you can configure count of fetching results per page by an appropriate configuration field. If you notice that 429s are coming back, you should reduce the limit until you start getting 200s. A sensible strategy for this is probably to iteratively halve the page size until you stop getting 429s.

Known limitations

  1. The component was not tested with the latest Lightspeed eCom version. Althouh it was fully tested with one the recent eCom releases, 100% compatibility can not be guaranteed

  2. The current version of the component doesn’t support next list of entities:

Lightspeed eCom API Documentation