Connected sources

GET/v1/shops/{id}/shopify/products

The products in the shop's Shopify, fifty at a time, as the Sources page lists them.

What it does

By title. Each call first lets the copy of the Shopify data catch up for a few seconds, at most 120 times an hour per person, so the list is fresh without spending the shop's own Shopify allowance.

Who may call it

A key whose maker's role holds figures (see the figures), after the fence, for the shop or category it names.

Request

HTTP
GET https://panlytics.net/api/v1/shops/{id}/shopify/products

Parameters

NameInTypeRequiredWhat it is
idpathintegerYesThe shop's id.
qquerystringNoOnly the rows whose title, SKU or barcode (orders: name) contain this.
cursorquerystringNoThe nextCursor of the page before.
AuthorizationheaderstringYesBearer, a space, then the key.

Example request

curl https://panlytics.net/api/v1/shops/12/shopify/products \
  -H "Authorization: Bearer $PANLYTICS_KEY"

Response

200: The answer, as JSON.

FieldTypeAlways thereWhat it is
data[]object[]YesUp to fifty rows.
data[].variantIdstringYesShopify's variant id.
data[].titlestringYesThe product and variant title.
data[].skustringYesThe SKU, or empty.
data[].barcodestringYesThe barcode, or empty.
data[].productTypestringYesThe Shopify product type, or empty.
data[].statusstringYesactive, draft or archived.
data[].pricenumberYesThe price.
data[].costnumber or nullYesThe cost price, or null.
data[].stocknumberYesPieces in stock.
data[].trackedbooleanYesTrue when Shopify tracks its stock.
nextCursorstring or nullYesSend it as cursor for the next page. Null on the last page.
currencystringYesThe shop's currency.

Example response

200
{
  "data": [
    {
      "variantId": "4410001",
      "title": "Oat milk 1 l",
      "sku": "OAT-1",
      "barcode": "6410000000017",
      "productType": "Beverages",
      "status": "active",
      "price": 2.49,
      "cost": 1.2,
      "stock": 14,
      "tracked": true
    }
  ],
  "nextCursor": null,
  "currency": "EUR"
}

Errors

A refusal is JSON with a code, a sentence in error, and a requestId when the fault is ours. Read the code, not the sentence. Every code is listed on Errors.

StatusCodeWhenWhat to do
400api.invalidA path id, a query parameter, a header or a body field is missing or not valid. detail names the field.Read that endpoint in the API reference, correct the field and call again.
401api.key_missingThe call had no Authorization header.Send the key in the Authorization header as Bearer, then call again.
401api.key_refusedThe key is wrong, revoked, past its end, or its maker or company no longer allows it (developer mode off, the maker removed or switched off, or the maker's role lost the developer ability).Ask the person who gave you the key to make a new one.
401api.wrong_key_kindThis key does not open these endpoints.Use the key these endpoints were made for, or ask the person who gave you the key.
403refusedThe key's maker may not do this here: their role lacks the ability, or the shop or category is outside their reach.Ask the CEO for a role that allows it, or call it for a shop or category the role reaches.
403auth.not_freshThis step needs you to prove it is you.Confirm your password or passkey, then try again.
404not_found.saidNothing with that id in the key's company. An id of another company answers the same.Check the id. List the shop or category it belongs to and take the id from there.
409source.noneNo source is connected to this shop.Connect one from Sources, then try again.
429api.rate_limitedThe key made more than 120 calls in this minute. Wait the seconds in Retry-After.Wait the seconds in Retry-After, then call again.
500serverSomething failed on our side. The answer carries a requestId to quote.Try again in a minute; if it keeps happening, report it.
503developer.unavailableAPI keys are not set up on this deployment yet.Report it, and we will switch them on.