Create an itemvariant

POST/commerce/{connection_id}/itemvariant

Parameters

fieldsstring array
Fields to return
rawstring
Raw parameters to include in the 3rd-party request. Encoded as a URL component. eg. raw parameters: foo=bar&zoo=bar -> raw=foo%3Dbar%26zoo%3Dbar
connection_idstring required
ID of the connection

Payload

idstring
created_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
namestring
public_namestring
descriptionstring
public_descriptionstring
skustring
barcode, UPC, isbn, etc
is_activeboolean
is_visibleboolean
is_featuredboolean
media array
available_atdate-time
(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
tagsstring array
widthnumber
heightnumber
lengthnumber
weightnumber
size_unit enum
Valid values:
"cm"
"inch"
weight_unit enum
Valid values:
"g"
"kg"
"oz"
"lb"
total_stocknumber
prices array
options array
inventory_idstring
requires_shippingboolean
metadata array
items array
references CommerceItem

Returns

Response fieldTypeRequiredDescription
idstringNo
created_atstring (date-time)No(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atstring (date-time)No(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
namestringNo
public_namestringNo
descriptionstringNo
public_descriptionstringNo
skustringNobarcode, UPC, isbn, etc
is_activebooleanNo
is_visiblebooleanNo
is_featuredbooleanNo
mediaCommerceItemMedia[]No
media[].idstringNo
media[].urlstringYes
media[].altstringNo
media[].typeenumNoValues: image, video
media[].heightnumberNo
media[].widthnumberNo
media[].positionnumberNo1 is the first
media[].metadataCommerceMetadata[]No
media[].metadata[].idstringNo
media[].metadata[].valueobjectNo
media[].metadata[].namespacestringNo
media[].metadata[].formatenumNoValues: TEXT, NUMBER, DATE, BOOLEAN, FILE, TEXTAREA, SINGLE_SELECT, MULTIPLE_SELECT, MEASUREMENT, PRICE, YES_NO, CURRENCY, URL
media[].metadata[].extra_dataobjectNo
media[].metadata[].slugstringNo
media[].metadata[].descriptionstringNo
media[].metadata[].is_requiredbooleanNo
available_atstring (date-time)No(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
tagsstring[]No
widthnumberNo
heightnumberNo
lengthnumberNo
weightnumberNo
size_unitenumNoValues: cm, inch
weight_unitenumNoValues: g, kg, oz, lb
total_stocknumberNo
pricesCommerceItemPrice[]No
prices[].pricenumberYes
prices[].compare_at_pricenumberNoThe original price of the item before an adjustment or a sale.
prices[].currencystringNo
optionsCommerceItemOption[]No
options[].idstringNo
options[].namestringYes
options[].positionnumberNo
options[].valuesstring[]Yes
inventory_idstringNo
requires_shippingbooleanNo
metadataCommerceMetadata[]No
metadata[].idstringNo
metadata[].valueobjectNo
metadata[].namespacestringNo
metadata[].formatenumNoValues: TEXT, NUMBER, DATE, BOOLEAN, FILE, TEXTAREA, SINGLE_SELECT, MULTIPLE_SELECT, MEASUREMENT, PRICE, YES_NO, CURRENCY, URL
metadata[].extra_dataobjectNo
metadata[].slugstringNo
metadata[].descriptionstringNo
metadata[].is_requiredbooleanNo
itemsCommerceReference[]Noreferences CommerceItem
items[].idstringNo
items[].namestringNo
items[].typestringNo

Errors

Errors return the HTTP status code and a JSON body with statusCode, error (the short label) and message (a human-readable detail).

{
  "statusCode": 429,
  "error": "Too Many Requests",
  "message": "Too many requests to unified.to API; max requests per minute: N"
}
StatusErrorMeaning
400Bad RequestThe request was malformed or failed validation.
401UnauthorizedThe connection is likely broken; re-authorize it.
403ForbiddenThe connection is missing permissions or scopes.
404Not FoundThe requested resource does not exist.
429Too Many RequestsRate limit exceeded (see the two sources below).
500Internal Server ErrorAn unexpected error occurred.
501Not ImplementedNot supported by this integration.

Errors from the underlying integration pass through: the integration's status comes back as ours (429, 401, 403, 404 or 5xx), usually with its message. When the integration's error body is unclear, Unified extracts what it can and returns a clearer message.

429 Too Many Requests

A 429 has two possible sources:

  • The integration's own rate limit, passed through.
  • Unified's workspace limit: a rolling 60 seconds, set by plan, with the message Too many requests to unified.to API; max requests per minute: N.
const options = {
  method: 'POST',
  url: 'https://api.unified.to/commerce/5de520f96e439b002043d8dc/itemvariant',
  headers: {
    authorization: 'bearer .....'
  },
  data: undefined,
  params: {
    fields: '',
    raw: '',
  }
};

const results = await axios.request(options);
Are we missing anything? Let us know
Was this page helpful?