Docs
Catalog API
Product variants
Metafields

Metafields

Get Product Variant Metafields

GET /catalog/products/{product_id}/variants/{variant_id}/metafields

Request

Returns a list of product variant Metafields. Optional parameters can be passed in.

Authentication

  • X-Auth-Token in header

Parameters

  • store_hash in path - string
  • Accept in header with default of application/json - string
    required
    The MIME type of the response body.
  • product_id in path - integer
    required

    The ID of the Product to which the resource belongs. Product variant metafield endpoints that have the product_id in the request path are successful as long as the parameter is not empty. The product_id segment is there only for path consistency.

  • variant_id in path - integer
    required

    ID of the variant on a product, or on an associated Price List Record.

  • include_fields in query - array
    Fields to include, in a comma-separated list. The ID and the specified fields will be returned.
    Type: array[string]
  • exclude_fields in query - array
    Fields to exclude, in a comma-separated list. The specified fields will be excluded from a response. The ID cannot be excluded.
    Type: array[string]
  • page in query - integer

    Specifies the page number in a limited (paginated) list of products.

  • limit in query - integer

    Controls the number of items per page in a limited (paginated) list of products.

  • key in query - string
    Filter based on a metafieldʼs key.
  • namespace in query - string
    Filter based on a metafieldʼs namespaces.

example

curl --request GET \
--url 'https://api.bigcommerce.com/stores/[store_hash]/v3/catalog/products/[product_id]/variants/[variant_id]/metafields' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--header 'X-Auth-Token: {{token}}'

Response

Body

object | application/json

  • data    array[object]

  • meta    object

    Returns the categories tree, a nested lineage of the categories with parent->child relationship. The Category objects returned are simplified versions of the category objects returned in the rest of this API.

example

{
"data": [
{
"key": "Location",
"value": "4HG",
"namespace": "Warehouse Locations",
"permission_set": "app_only",
"description": "Location in the warehouse",
"resource_type": "product",
"resource_id": 111
}
],
"meta": {
"data": [
{
"id": 26,
"parent_id": 25,
"name": "Bath",
"is_visible": true,
"url": "/towels/bath-towels/"
}
],
"meta": {}
}
}

Create a Product Variant Metafield

POST /catalog/products/{product_id}/variants/{variant_id}/metafields

Request

Creates a product variant Metafield.

Required Fields:

  • permission_set
  • namespace
  • key
  • value

Read-Only Fields

  • id

Note: The maxiumum number of metafields allowed on each order, product, category, variant, or brand is 250 per client ID. For more information, see Platform Limits in the Help Center.

Authentication

  • X-Auth-Token in header

Parameters

  • store_hash in path - string
  • Accept in header with default of application/json - string
    required
    The MIME type of the response body.
  • product_id in path - integer
    required

    The ID of the Product to which the resource belongs. Product variant metafield endpoints that have the product_id in the request path are successful as long as the parameter is not empty. The product_id segment is there only for path consistency.

  • variant_id in path - integer
    required

    ID of the variant on a product, or on an associated Price List Record.

  • Content-Type in header with default of application/json - string
    required
    The MIME type of the request body.

Body

object | application/json
Metafield for products, categories, variants, and brands; the max number of metafields allowed on each is 50. For more information, see Platform Limits in the Help Center.

  • key    string
    required

    The name of the field, for example: location_id, color. Required for POST.

    >= 1 characters<= 64 characters
    Example: Location

  • value    string
    required

    The value of the field, for example: 1, blue. You must enter a JSON formatted string for ShipperHQ metafields. Required for POST.

    >= 1 characters<= 65535 characters
    Example: 4HG

  • namespace    string
    required

    Namespace for the metafield, for organizational purposes. This is set by the developer. Required for POST.

    >= 1 characters<= 64 characters
    Example: Warehouse Locations

  • permission_set    string
    required

    Determines the visibility and writeability of the field by other API consumers.

    ValueDescription
    app_onlyPrivate to the app that owns the field
    readVisible to other API consumers
    writeOpen for reading and writing by other API consumers
    read_and_sf_accessVisible to other API consumers, including on storefront
    write_and_sf_accessOpen for reading and writing by other API consumers, including on storefront

    Allowed: app_only | read | write | read_and_sf_access | write_and_sf_access

  • description    string

    Description for the metafields.

    >= 1 characters<= 255 characters
    Example: Location in the warehouse

example

{
"key": "Location",
"value": "4HG",
"namespace": "Warehouse Locations",
"permission_set": "app_only",
"description": "Location in the warehouse"
}

Response

Body

object | application/json

  • data    object

    Metafield for products, categories, variants, and brands; the max number of metafields allowed on each is 50. For more information, see Platform Limits in the Help Center.

  • meta    object

    Response metadata.

example

{
"data": {
"id": 4,
"key": "location_id",
"value": "Shelf 3, Bin 5",
"namespace": "App Namespace",
"permission_set": "app_only",
"resource_type": "variant",
"resource_id": 137,
"description": "Where products are located",
"date_created": "2021-08-06T19:15:35+00:00",
"date_modified": "2021-08-06T19:15:35+00:00"
},
"meta": {}
}

Get a Product Variant Metafields

GET /catalog/products/{product_id}/variants/{variant_id}/metafields/{metafield_id}

Request

Returns a single product variant Metafield. Optional parameters can be passed in.

Authentication

  • X-Auth-Token in header

Parameters

  • store_hash in path - string
  • Accept in header with default of application/json - string
    required
    The MIME type of the response body.
  • product_id in path - integer
    required

    The ID of the Product to which the resource belongs. Product variant metafield endpoints that have the product_id in the request path are successful as long as the parameter is not empty. The product_id segment is there only for path consistency.

  • variant_id in path - integer
    required

    ID of the variant on a product, or on an associated Price List Record.

  • metafield_id in path - integer
    required

    The ID of the Metafield.

  • include_fields in query - array
    Fields to include, in a comma-separated list. The ID and the specified fields will be returned.
    Type: array[string]
  • exclude_fields in query - array
    Fields to exclude, in a comma-separated list. The specified fields will be excluded from a response. The ID cannot be excluded.
    Type: array[string]

example

curl --request GET \
--url 'https://api.bigcommerce.com/stores/[store_hash]/v3/catalog/products/[product_id]/variants/[variant_id]/metafields/[metafield_id]' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--header 'X-Auth-Token: {{token}}'

Response

Body

object | application/json

  • data    object

    Metafield for products, categories, variants, and brands; the max number of metafields allowed on each is 50. For more information, see Platform Limits in the Help Center.

  • meta    object

    Response metadata.

example

{
"data": {
"id": 8,
"key": "location_id",
"value": "Shelf 3, Bin 5",
"namespace": "Inventory Namespace",
"permission_set": "read",
"resource_type": "variant",
"resource_id": 158,
"description": "Where products are located",
"date_created": "2018-09-13T16:42:37+00:00",
"date_modified": "2018-09-13T16:42:37+00:00"
},
"meta": {}
}

Update Product Variant Metafields

PUT /catalog/products/{product_id}/variants/{variant_id}/metafields/{metafield_id}

Request

Updates a product variant Metafield.

Required Fields:

  • none

Read-Only Fields

  • id
  • These fields can only be modified by the app (API credentials) that created the metafield:
    • namespace
    • key
    • permission_set

Usage Notes

  • Attempting to modify namespace, key, and permission_set fields using a client ID different from the one used to create those metafields will result in a 403 error message.

Authentication

  • X-Auth-Token in header

Parameters

  • store_hash in path - string
  • Accept in header with default of application/json - string
    required
    The MIME type of the response body.
  • product_id in path - integer
    required

    The ID of the Product to which the resource belongs. Product variant metafield endpoints that have the product_id in the request path are successful as long as the parameter is not empty. The product_id segment is there only for path consistency.

  • variant_id in path - integer
    required

    ID of the variant on a product, or on an associated Price List Record.

  • metafield_id in path - integer
    required

    The ID of the Metafield.

  • Content-Type in header with default of application/json - string
    required
    The MIME type of the request body.

Body

object | application/json
Metafield for products, categories, variants, and brands; the max number of metafields allowed on each is 50. For more information, see Platform Limits in the Help Center.

  • key    string
    required

    The name of the field, for example: location_id, color. Required for POST.

    >= 1 characters<= 64 characters
    Example: Location

  • value    string
    required

    The value of the field, for example: 1, blue. You must enter a JSON formatted string for ShipperHQ metafields. Required for POST.

    >= 1 characters<= 65535 characters
    Example: 4HG

  • namespace    string
    required

    Namespace for the metafield, for organizational purposes. This is set by the developer. Required for POST.

    >= 1 characters<= 64 characters
    Example: Warehouse Locations

  • permission_set    string
    required

    Determines the visibility and writeability of the field by other API consumers.

    ValueDescription
    app_onlyPrivate to the app that owns the field
    readVisible to other API consumers
    writeOpen for reading and writing by other API consumers
    read_and_sf_accessVisible to other API consumers, including on storefront
    write_and_sf_accessOpen for reading and writing by other API consumers, including on storefront

    Allowed: app_only | read | write | read_and_sf_access | write_and_sf_access

  • description    string

    Description for the metafields.

    >= 1 characters<= 255 characters
    Example: Location in the warehouse

example

{
"key": "Location",
"value": "4HG",
"namespace": "Warehouse Locations",
"permission_set": "app_only",
"description": "Location in the warehouse"
}

Response

Body

object | application/json

  • data    object

    Metafield for products, categories, variants, and brands; the max number of metafields allowed on each is 50. For more information, see Platform Limits in the Help Center.

  • meta    object

    Response metadata.

example

{
"data": {
"id": 8,
"key": "location_id",
"value": "Shelf 3, Bin 5",
"namespace": "Inventory Namespace",
"permission_set": "read",
"resource_type": "variant",
"resource_id": 158,
"description": "Where products are located",
"date_created": "2018-09-13T16:42:37+00:00",
"date_modified": "2018-09-13T16:42:37+00:00"
},
"meta": {}
}

Delete a Product Variant Metafield

DELETE /catalog/products/{product_id}/variants/{variant_id}/metafields/{metafield_id}

Request

Deletes a product variant Metafield.

Authentication

  • X-Auth-Token in header

Parameters

  • store_hash in path - string
  • Accept in header with default of application/json - string
    required
    The MIME type of the response body.
  • product_id in path - integer
    required

    The ID of the Product to which the resource belongs. Product variant metafield endpoints that have the product_id in the request path are successful as long as the parameter is not empty. The product_id segment is there only for path consistency.

  • variant_id in path - integer
    required

    ID of the variant on a product, or on an associated Price List Record.

  • metafield_id in path - integer
    required

    The ID of the Metafield.

example

curl --request DELETE \
--url 'https://api.bigcommerce.com/stores/[store_hash]/v3/catalog/products/[product_id]/variants/[variant_id]/metafields/[metafield_id]' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--header 'X-Auth-Token: {{token}}'

Response

Did you find what you were looking for?
Create a Product Variant ImageGet Product Variant Metafields