Testing Product-Based Shopping Experience APIs in production

This guide can be used as a reference for testing Phase 2 functionality and flows in the Production environment for Product-Based Shopping Experience (PBSE) related APIs. It provides the list of Production test categories, describes the use cases available for testing and their examples, and will help you to quickly adopt Phase 2 capabilities of PBSE.

Table of Contents

Available test categories in Production environment

Test leaf categories have been added to the Production environment for the US, UK, Australia, and Canada sites. The test leaf categories are mirrors of actual eBay categories on these sites. There are three sets of categories for each marketplace (AU, US, UK, CA[English]): PBSE-enforced, PBSE-enabled, and Non-PBSE.

  • For PBSE-enforced test categories, association with an eBay Catalog product is required. Listings with no ePIDs associated will not be allowed, and listing new items or revising existing items will fail with an error.
  • For PBSE-enabled test categories, association with an eBay Catalog product is supported but optional. You can submit change requests to create or modify eBay catalog products and will be allowed to list an item without associating a product with the listing itself.
  • For non-PBSE test categories, All of the test categories have instance aspects (if applicable for the category), but some of the test categories do not return product aspects. There is a column in the table that denotes whether the test category returns product aspects (specifics).

All of the available test categories have instance aspects (if applicable for the category), but some of the test categories do not return product aspects. There is a column in each table that denotes whether or not the test category returns product aspects.

See Production test leaf categories for testing PBSE use cases for detailed information about the test categories.

Test cases in this document

Developers and sellers can do the following Phase 2 testing with the test categories:

  • Use the getProductAdoptionPolicies method or the GetCategoryFeatures call to see if test category requires association with catalog product.
  • Use the getProductMetadataForCategories method to see required/recommended product aspects for test category.
  • Use the getProductMetadata method to see the required/recommended product aspects when associated to given test categories.
  • Use the createChangeRequest method to make a request to add a new product to the eBay catalog in one or more of the test categories.
  • Use the createChangeRequest method to make a request to revise an existing catalog product in one of the test categories.
  • Use the Inventory API methods or the Trading API methods to create or revise listings and associated them with catalog products test categories.
  • Use the getItemAspectsForCategory method of the Taxonomy API or the GetCategorySpecifics call of the Trading API to look for supported instance specifics in the test category.
  • Experiment with the change_request methods of the Catalog API to submit and retrieve different change request statuses.
  • Create new listings with the Inventory API methods or the AddItem call of the Trading API to initiate and check for different warnings and error messages.

This document describes the preceding test cases in detail.

Retrieve eBay supported product adoption policies

Use the Metadata API's getProductAdoptionPolicies call to retrieve information about all categories in an eBay marketplace, indicating whether listings in each category require adoption of a catalog product.

GET https://api.ebay.com/sell/metadata/v1/marketplace/EBAY_US/get_product_adoption_policies

The following snippet shows that listings in three EBAY_US categories must adopt a catalog product, and the fourth category does not (the productRequired field has a value of false or is not returned at all).

...
{
    "categoryTreeId": "0",
    "categoryId": "178114",
    "productRequired": true
},
{
    "categoryTreeId": "0",
    "categoryId": "178115",
    "productRequired": true
},
{
    "categoryTreeId": "0",
    "categoryId": "178116",
    "productRequired": true
},
{
    "categoryTreeId": "0",
    "categoryId": "179450"
},
...

Note: This call can return a very large response payload. We strongly recommend that you get the results from this call in a GZIP file by including the following HTTP header with your request: Accept-Encoding: application/gzip

Retrieve supported aspects for a category

Use the Catalog API's getProductMetadataForCategories call to retrieve an array of all supported aspects, aspect constraints, and aspect values for eBay test category ID 178115. The array is a union (with duplicates removed) of all returned aspects.

GET https://api.ebay.com/commerce/catalog/v1_beta/get_product_metadata_for_categories?primary_category_id=178115

The following snippet describes one aspect returned in the output (you can see an entire payload in the call reference sample):

...
{
  “name”: “Base Material”,
  “constraint”: {
    “aspectDataType”: “STRING”,
    “productToAspectCardinality”: “SINGLE”,
    “aspectMode”: “FREE_TEXT”,
    “aspectRequired”: false
  },
  “values”: [
    {
      “value”: “Fabric”
    },
    {
      “value”: “Metal”
    }
  ]
},
...

Retrieve supported aspects for a product

The Catalog API's getProductMetadata call retrieves an array of all supported aspects, aspect constraints, and aspect values for the catalog product with ePID 26020409399 and several test categories (ID's 178114, 178116,178120), as well as the values currently associated with that product. The array is a union (with duplicates removed) of the aspects for three catagories.

You can use this call to discover the available aspects when additional categories are associated with the product.

GET https://api.ebay.com/commerce/catalog/v1_beta/get_product_metadata?epid=26020409399&primary_category_id=178114&other_applicable_category_ids=178116,178120

The following snippet describes one aspect returned in the output (you can see an entire payload in the call reference sample):

…
"aspects": [
  {
    "name": "Model",
    "valuesAssociatedWithProduct": [
      "iPhone 20"
    ],
    "constraint": {
      "aspectDataType": "STRING",
      "productToAspectCardinality": "SINGLE",
      "aspectMode": "FREE_TEXT",
      "aspectRequired": false
    },
    "values": [
      {
        "value": "ASUS PadFone 2"
      },
      {
        "value": "ASUS PadFone S"
      },
...

Adding a catalog product to a test category

The next several sections give specific examples of submitting catalog change requests for test categories. Each example demonstrates how users can trigger different statuses when they make getChangeRequest calls.

The createChangeRequest method is used to make a request to add a new product to the eBay Catalog in one of the test categories. In the following examples, be sure to set the changeRequestType field to PRODUCT_CREATION. The examples demonstrate calls that produce various values in the changeRequestStatus field of the getChangeRequest response.

Note: Red text in the following examples indicates significant values to use in a request or to note in a response.

New product is approved

Make the createChangeRequest call to trigger an APPROVED status.

POST http://api.ebay.com/commerce/catalog/v1/change_request

Request payload:

{
  "changeRequestType": "PRODUCT_CREATION",
  "reasonForChangeRequest": "Request to add new product",
  "suggestedProduct": {
    "title": "Test Approved Status",
    "description": "",
    "primaryCategoryId": "178115",
    "aspects": [
        {
          "name": "Features",
          "values": ["3G Data Capable, 4G Data Capable"]
        }
    ],
    "imageUrl": "https://i.ebayimg.com/00/s/NDczWDMyNQ==/z/
-6IAAOSwY45UPAWE/$_6.JPG?set_id=89040003C1", "brand": "Apple", "upc": ["0745577656433"], "mpn": ["MD295LL/A"] } }

A Location HTTP header is returned with the full endpoint to retrieve status of the catalog change request. The unique catalog change request identifier is appended to the end of the endpoint, and this identifier should be captured and stored.

Note: This request ID value is specific to the user, so the one you receive will be different.

Call getChangeRequest to get the status of the product creation request. The status should be APPROVED, and an ePID and eBay product page URL should also be returned in the response.

GET https://api.ebay.com/commerce/catalog/v1_beta/ change_request/5b22ed268702d13a07161d1c

Response payload:

{
  “changeRequestId”: "5b22ed268702d13a07161d1c",
  “changeRequestType”: “PRODUCT_CREATION”,
  “changeRequestStatus”: “APPROVED”,
  “creationDate”: “2018-09-14T22:33:10.740Z”,
  “reasonForChangeRequest”: “Request to add new product”,
  “resolutionDate”: “2018-09-14T22:33:13.160Z”,
  “suggestedProduct”: {
    “title”: “Test Approved Status”,
    “description”: “",
    “primaryCategoryId”: “178115",
    “aspects”: [
      {
	"name": "Features",
	"values": ["3G Data Capable, 4G Data Capable"]
      }
    ],
    “imageUrl”: “https://i.ebayimg.com/00/s/NDczWDMyNQ==/z/
-6IAAOSwY45UPAWE/$_6.JPG?set_id=89040003C1“, "brand": "Apple", "upc": ["0745577656433"], "mpn": ["MD295LL/A"] }, “processResolution”: { “epid”: “3023890567”, “productHref”: “https://api.ebay.com/commerce/catalog/
v1_beta/product/3023890567
” } }

Call getProduct to inspect the complete product details of the catalog product that was returned in the getChangeRequest response. The ePID value is passed in at the end of the call URI, like below.

GET https://api.ebay.com/commerce/catalog/v1_beta/product/3023890567

Response payload:

   {
     "aspects": [
       {
         "localizedName": "GTIN",
         "localizedValues": [
           "0745577656433"
         ]
       },
       {
         "localizedName": "BRAND",
         "localizedValues": [
           "Apple"
         ]
       },
       {
         "localizedName": "MPN",
         "localizedValues": [
           "MD295LL/A"
         ]
       },
       {
         "localizedName": "UPC",
         "localizedValues": [
           "0745577656433"
         ]
       },
       {
         "localizedName": "Features",
         "localizedValues": [
           "3G Data Capable",
           "4G Data Capable"
         ]
       }
     ],
     "title": "Test Approved Status",
     "version": "0",
     "image": {
       "imageUrl": "https://i.ebayimg.com/00/s/NDczWDMyNQ==/z/
-6IAAOSwY45UPAWE/$_57.JPG?set_id=89040003C1" }, "gtin": [ "0745577656433" ], "mpn": [ "MD295LL/A" ], "upc": [ "0745577656433" ], "brand": "Apple", "epid": "3023890567", "productWebUrl": "https://www.ebay.com/p/Test+Approved+Status/3023890567", "primaryCategoryId": "178115" }

New product is approved with modifications (Aspect typo)

Make the following createChangeRequest call to create a product creation request that will trigger an APPROVED_WITH_MODIFICATIONS status.

POST http://api.ebay.com/commerce/catalog/v1/change_request

Request payload:

{
   “changeRequestType”: “PRODUCT_CREATION”,
   “reasonForChangeRequest”: “Request to add new product”,
   “suggestedProduct”: {
    “title”: “”,
    “description”: “",
    “primaryCategoryId”: “178115",
    “aspects”: [
        {
        “name”: “Color”,
        “values”: [“Blaaaack”]
        }
    ],
    “imageUrl”: “https://i.ebayimg.com/00/
6.JPG?set_id=89040003C1C1“, “brand”: “Apple”, “upc”: [“0745577656433"], “mpn”: [“MD295LL/A”] } }

A Location HTTP header is returned with the full endpoint to retrieve status of the catalog change request. The unique catalog change request identifier is appended to the end of the endpoint, and this identifier should be captured/stored.

GET https://api.ebay.com/commerce/catalog/v1_beta/change_request/5b22fdf28702d13a07161d22

Note: This request ID value is specific to the user, so the one you receive will be different.

Call getChangeRequest to get the status of the product creation request. The status should be APPROVED_WITH_MODIFICATIONS, and information on the modification that eBay made is also returned. And since the change request was approved, an ePID and eBay product page URL is also returned in the response.

GET https://api.ebay.com/commerce/catalog/v1_beta/ change_request/5b22fdf28702d13a07161d22

Response payload:

{
    "changeRequestId": "5b22fdf28702d13a07161d22",
    "changeRequestType": "PRODUCT_CREATION",
    "changeRequestStatus": "APPROVED_WITH_MODIFICATIONS",
    "creationDate": "2018-09-14T23:44:50.777Z",
    "reasonForChangeRequest": "Request to add new product",
    "resolutionDate": "2018-09-14T23:44:51.643Z",
    "suggestedProduct": {
        "title": "",
        "description": "",
        "primaryCategoryId": "178115",
        "aspects": [
            {
                "name": "Color",
                "values": [
                    "Blaaaack"
                ]
            }
        ],
        "imageUrl": "https://i.ebayimg.com/00/
6.JPG?set_id=89040003C1C1", "brand": "Apple", "mpn": [ "MD295LL/A" ], "upc": [ "0745577656433" ] }, "processResolution": { "epid": "20023921587", "productHref": "https://api.ebay.com/commerce/catalog/
v1_beta/product/20023921587
", "corrections": [ { "correctionCode": "1901", "reason": "We updated the Color for this product,
but we changed the Blaaaack you submitted to Black.", "aspectValues": { "aspectName": "Color", "values": [ { "value": "Blaaaack", "newValue": "Black" } ] } } ] } }

Call getProduct to inspect the complete product details of the catalog product that was returned in the getChangeRequest response. The ePID value is passed in at the end of the call URI, like below.

GET https://api.ebay.com/commerce/catalog/v1_beta/product/3020418775

Response payload:

{
  "aspects": [
    {
      "localizedName": "GTIN",
      "localizedValues": [
        "0745577656433"
      ]
    },
    {
      "localizedName": "BRAND",
      "localizedValues": [
        "Apple"
      ]
    },
    {
      "localizedName": "MPN",
      "localizedValues": [
        "MD295LL/A"
      ]
    },
    {
      "localizedName": "UPC",
      "localizedValues": [
        "0745577656433"
      ]
    },
    {
      "localizedName": "Color",
      "localizedValues": [
        "Black"
      ]
    }
  ],
  "title": "SNOY",
  "version": "0",
  "image": {
    "imageUrl": "https://i.ebayimg.com/images/g/HFAAAOSw9W5bWgcQ/s-l1768900.jpg?set_id=89040003C1C1"
  },
  "gtin": [
    "0745577656433"
  ],
  "mpn": [
    "MD295LL/A"
  ],
  "upc": [
    "0745577656433"
  ],
  "brand": "Apple",
  "epid": "20023921587",
  "productWebUrl": "https://www.ebay.com/p/SNOY/20023921587",
  "primaryCategoryId": "178115"
}

New product is approved with modifications (Title typo)

Make the following createChangeRequest call to create a product creation request that will trigger an APPROVED_WITH_MODIFICATIONS status.

POST http://api.ebay.com/commerce/catalog/v1/change_request

Request payload:

{
    “changeRequestType”: “PRODUCT_CREATION”,
    “reasonForChangeRequest”: “Request to add new product”,
    “suggestedProduct”: {
     “title”: “SNOY”,
     “description”: “",
     “primaryCategoryId”: “178115",
     “aspects”: [
         {
         "name": "Features",
		 "values": ["3G Data Capable, 4G Data Capable"]
         }
     ],
     “imageUrl”: “https://i.ebayimg.com/00/
6.JPG?set_id=89040003C1C1“, “brand”: “Apple”, “upc”: [“0745577656433"], “mpn”: [“MD295LL/A”] } }

A Location HTTP header is returned with the full endpoint to retrieve status of the catalog change request. The unique catalog change request identifier is appended to the end of the endpoint, and this identifier should be captured/stored

GET https://api.ebay.com/commerce/catalog/v1_beta/
change_request/5ba126bf1609de236f5a138c

Note: This request ID value is specific to the user, so the one you receive will be different.

Call getChangeRequest to get the status of the product creation request. The status should be APPROVED_WITH_MODIFICATIONS, and information on the modification that eBay made is also returned. And since the change request was approved, an ePID and eBay product page URL is also returned in the response.

GET https://api.ebay.com/commerce/catalog/v1_beta/
change_request/5b22fdf28702d13a07161d22

Response payload:

{
     "changeRequestId": "5ba126bf1609de236f5a138c",
     "changeRequestType": "PRODUCT_CREATION",
     "changeRequestStatus": "APPROVED_WITH_MODIFICATIONS",
     "creationDate": "2018-09-14T23:44:50.777Z",
     "reasonForChangeRequest": "Request to add new product",
     "resolutionDate": "2018-09-14T23:44:51.643Z",
     "suggestedProduct": {
         "title": "SNOY",
         "primaryCategoryId": "178115",
         "aspects": [
           {
            "name": "Features",
            "values": ["3G Data Capable, 4G Data Capable"]
           }
         ],
         "imageUrl": "https://i.ebayimg.com/00/
6.JPG?set_id=89040003C1C1", "brand": "Apple", "mpn": [ "MD295LL/A" ], "upc": [ "0745577656433" ] }, "processResolution": { "epid": "6023918604", "productHref": "https://api.ebay.com/commerce/catalog/
v1_beta/product/6023918604
", "corrections": [ { "correctionCode": "1002", "reason": "We updated the title for this product.
It may not match the product title you submitted.", "productAttribute": { "attributeName": "TITLE", "value": "SNOY", "newValue": "SONY" } } ] } }

Call getProduct to inspect the complete product details.

GET https://api.ebay.com/commerce/catalog/v1_beta/product/6023918604

Response payload:

{
   "aspects": [
       {
         "localizedName": "GTIN",
         "localizedValues": [
           "0745577656433"
         ]
       },
       {
         "localizedName": "BRAND",
         "localizedValues": [
           "Apple"
         ]
       },
       {
         "localizedName": "MPN",
         "localizedValues": [
           "MD295LL/A"
         ]
       },
       {
         "localizedName": "UPC",
         "localizedValues": [
           "0745577656433"
         ]
       },
       {
         "localizedName": "Features",
         "localizedValues": [
           "3G Data Capable, 4G Data Capable"
         ]
       }
     ],
     "title": "SONY",
     "version": "0",
     "image": {
       "imageUrl": "https://i.ebayimg.com/images/g/HFAAAOSw9W5bWgcQ/s-l1600.jpg?set_id=89040003C1C1"
     },
     "gtin": [
       "0745577656433"
     ],
     "mpn": [
       "MD295LL/A"
     ],
     "upc": [
       "0745577656433"
     ],
     "brand": "Apple",
     "epid": "6023918604",
     "productWebUrl": "https://www.ebay.com/p/SONY/6023918604",
     "primaryCategoryId": "178115"
 }

Verifying catalog product changes

Once your change request has been approved (with or without modifications), you should be able to see the result on eBay. Use the following URL format to view the product page for the newly created catalog product:

https://www.ebay.com/p/epid

Where epid is the product ID returned in the approved getChangeRequest response. From the above examples:

  • https://www.ebay.com/p/20023921587
  • https://www.ebay.com/p/6023918604

New product request has SUBMITTED status

Make the following createChangeRequest call to create a product creation request that will trigger a SUBMITTED status.

POST https://api.ebay.com/commerce/catalog/v1_beta/change_request

Request payload:

{
  "changeRequestType": "PRODUCT_CREATION",
  "reasonForChangeRequest": "Request to add new product",
  "suggestedProduct": {
    "title": "submitted",
    "description": "",
    "primaryCategoryId": "178115",
    "aspects": [
       {
        "name": "Features",
        "values": ["4G Data Capable"]
       }
     ],
    "imageUrl": "https://i.ebayimg.com/00/6.JPG?set_id=89040003C1",
    "brand": "Apple",
    "upc": ["0745577656433"],
    "ean": ["0885909530199"],
    "mpn": ["MD295LL/A"]
  }
}

A Location HTTP header is returned with the full endpoint to retrieve status of the catalog change request. The unique catalog change request identifier is appended to the end of the endpoint, and this identifier should be captured and stored.

GET https://api.ebay.com/commerce/catalog/v1_beta/change_request/5ba12bc11609de236f5a1397

Note: This request ID value is specific to the user, so the one you receive will be different.

Call getChangeRequest to get the status of the product creation request. The status should be SUBMITTED.

GET https://api.ebay.com/commerce/catalog/v1_beta/change_request/5ba12bc11609de236f5a1397

Response payload:

{
  "changeRequestId": "5ba12bc11609de236f5a1397",
  "changeRequestType": "PRODUCT_CREATION",
  "changeRequestStatus": "SUBMITTED",
  "creationDate": "2018-09-14T22:51:31.509Z",
  "reasonForChangeRequest": "Request to add new product",
  "resolutionDate": "2018-09-14T22:51:31.610Z",
  "suggestedProduct": {
    "title": "submitted",
    "primaryCategoryId": "178115",
    "aspects": [
      {
        "name": "Features",
        "values": ["4G Data Capable"]
      }
    ],
    "imageUrl": "https://i.ebayimg.com/00/6.JPG?set_id=89040003C1",
    "brand": "Apple",
    "mpn": [
      "MD295LL/A"
    ],
    "ean": [
      "0885909530199"
    ],
    "upc": [
      "0745577656433"
    ]
  },
  "processResolution": {
     "productHref": null
  }
}

New product request has UNDER_REVIEW status

Make the following createChangeRequest call to create a product creation request that will trigger an UNDER_REVIEW status.

POST https://api.ebay.com/commerce/catalog/v1_beta/change_request

Request payload:

{
  "changeRequestType": "PRODUCT_CREATION",
  "reasonForChangeRequest": "Request to add new product",
  "suggestedProduct": {
    "title": "auto-decider:low-confidence",
    "description": "",
    "primaryCategoryId": "178115",
    "aspects": [
       {
        "name": "Features",
        "values": ["4G Data Capable"]
       }
     ],
    "imageUrl": "https://i.ebayimg.com/00/6.JPG?set_id=89040003C1",
    "brand": "Apple",
    "upc": ["0745577656433"],
    "ean": ["0885909530199"],
    "mpn": ["MD295LL/A"]
  }
}

A Location HTTP header is returned with the full endpoint to retrieve status of the catalog change request. The unique catalog change request identifier is appended to the end of the endpoint, and this identifier should be captured and stored.

GET https://api.ebay.com/commerce/catalog/v1_beta/change_request/5ba12dfa61c52c0c1c936b65

Note: This request ID value is specific to the user, so the one you receive will be different.

Call getChangeRequest to get the status of the product creation request. The status should be UNDER_REVIEW.

GET https://api.ebay.com/commerce/catalog/v1_beta/change_request/5ba12dfa61c52c0c1c936b65

Response payload:

{
    "changeRequestId": "5ba12dfa61c52c0c1c936b65",
    "changeRequestType": "PRODUCT_CREATION",
    "changeRequestStatus": "UNDER_REVIEW",
    "creationDate": "2018-09-18T16:55:22.364Z",
    "reasonForChangeRequest": "Request to add new product",
    "resolutionDate": "2018-09-18T16:55:22.831Z",
    "suggestedProduct": {
      "title": "auto-decider:low-confidence",
      "primaryCategoryId": "178115",
      "aspects": [
        {
          "name": "Features",
          "values": [
            "4G Data Capable"
          ]
        }
      ],
      "imageUrl": "https://i.ebayimg.com/images/g/
HFAAAOSw9W5bWgcQ/s-l1600.jpg?set_id=89040003C1C1", "brand": "Apple", "mpn": [ "MD295LL/A" ], "upc": [ "0745577656433" ] }, "processResolution": { "productHref": null } }

New product request has UNDER_EXTENDED_REVIEW status

Make the following createChangeRequest call to create a product creation request that will trigger an UNDER_EXTENDED_REVIEW status.

POST https://api.ebay.com/commerce/catalog/v1_beta/change_request

Request payload:

{
  "changeRequestType": "PRODUCT_CREATION",
  "reasonForChangeRequest": "Request to add new product",
  "suggestedProduct": {
	"title": "How to optimize for free shipping",
	"description": "",
	"primaryCategoryId": "178115",
	"aspects": [
	   {
		"name": "Features",
		"values": ["4G Data Capable"]
	   }
	 ],
	"imageUrl": "https://i.ebayimg.com/00/6.JPG?set_id=89040003C1",
	"brand": "Apple",
	"upc": ["0745577656433"],
	"ean": ["0885909530199"],
	"mpn": ["MD295LL/A"]
  }
}

A Location HTTP header is returned with the full endpoint to retrieve status of the catalog change request. The unique catalog change request identifier is appended to the end of the endpoint, and this identifier should be captured and stored.

GET https://api.ebay.com/commerce/catalog/v1_beta/change_request/5ba12fbe5d35ea4c0eae2692

Note: This request ID value is specific to the user, so the one you receive will be different.

Call getChangeRequest to get the status of the product creation request. The status should be UNDER_EXTENDED_REVIEW.

GET https://api.ebay.com/commerce/catalog/v1_beta/change_request/5ba12fbe5d35ea4c0eae2692

Response payload:

{
"changeRequestId": "5ba12fbe5d35ea4c0eae2692",
"changeRequestType": "PRODUCT_CREATION",
"changeRequestStatus": "UNDER_EXTENDED_REVIEW",
"creationDate": "2018-09-18T16:55:22.364Z",
"reasonForChangeRequest": "Request to add new product",
"resolutionDate": "2018-09-18T16:55:22.831Z",
"suggestedProduct": {
  "title": "How to optimize for free shipping",
  "primaryCategoryId": "178115",
  "aspects": [
	{
	  "name": "Features",
	  "values": [
		"4G Data Capable"
	  ]
	}
  ],
  "imageUrl": "https://i.ebayimg.com/images/g/
HFAAAOSw9W5bWgcQ/s-l1600.jpg?set_id=89040003C1C1", "brand": "Apple", "mpn": [ "MD295LL/A" ], "upc": [ "0745577656433" ] }, "processResolution": { "productHref": null } }

New product request is rejected (Invalid Title)

Make the following createChangeRequest call to create a product creation request that will trigger a REJECTED status.

POST https://api.ebay.com/commerce/catalog/v1_beta/change_request

Request payload:

{
"changeRequestType": "PRODUCT_CREATION",
  "reasonForChangeRequest": "Request to add new product",
  "suggestedProduct": {
	"title": "auto-decider:reject",
	"description": "",
	"primaryCategoryId": "178115",
	"aspects": [
		{
		  "name": "Features",
		  "values": ["4G Data Capable"]
		}
	],
	"imageUrl": "https://i.ebayimg.com/images/g/
HFAAAOSw9W5bWgcQ/s-l1600.jpg?set_id=89040003C1C1", "brand": "Apple", "upc": ["0745577656433"], "mpn": ["MD295LL/A"] } }

A Location HTTP header is returned with the full endpoint to retrieve status of the catalog change request. The unique catalog change request identifier is appended to the end of the endpoint, and this identifier should be captured and stored.

GET https://api.ebay.com/commerce/catalog/v1_beta/change_request/5ba13be761c52c0c1c936b73

Note: This request ID value is specific to the user, so the one you receive will be different.

Call getChangeRequest to get the status of the product creation request. The status should be REJECTED, and the reason for the rejection should also be returned in the response.

GET https://api.ebay.com/commerce/catalog/v1_beta/
change_request/5ba13be761c52c0c1c936b73

Response payload:

{
"changeRequestId": "5ba13be761c52c0c1c936b73",
  "changeRequestType": "PRODUCT_CREATION",
  "changeRequestStatus": "REJECTED",
  "creationDate": "2018-09-18T17:54:47.323Z",
  "reasonForChangeRequest": "Request to add new product",
  "resolutionDate": "2018-09-18T17:54:47.863Z",
  "suggestedProduct": {
    "title": "auto-decider:reject",
    "primaryCategoryId": "178115",
    "aspects": [
      {
        "name": "Features",
        "values": [
          "4G Data Capable"
        ]
      }
    ],
    "imageUrl": "https://i.ebayimg.com/images/g/
HFAAAOSw9W5bWgcQ/s-l1600.jpg?set_id=89040003C1C1", "brand": "Apple", "mpn": [ "MD295LL/A" ], "upc": [ "0745577656433" ] }, "processResolution": { "productHref": null, "violations": [ { "violationCode": "1", "reason": "The application has encountered an issue in the request", "productAttribute": { "values": [ "auto-decider:reject" ], "name": "TITLE" } } ] }

Note: When a test change request is rejected, all possible violations are returned. In real world use, only the violations that apply to this request would be returned.

New product request is rejected (Multiple Errors)

Call createChangeRequest to make a product creation request that is rejected. This particular reject test case introduces several types of errors (reasons for rejection), including the following:

  • Missing image URL
  • Title length exceeds maximum length allowed
  • Invalid MPN value
  • Invalid UPC value
  • Invalid Brand value
  • Aspect name exceeds maximum length allowed
  • Aspect value exceeds maximum length allowed

POST https://api.ebay.com/commerce/catalog/v1_beta/change_request

Request payload:

{
"changeRequestType": "PRODUCT_CREATION",
 "reasonForChangeRequest": "Request to add new product",
 "suggestedProduct": {
   "title": "1234567890123456789012345678901234567890123456789012
345678901234567890123456789012345678901234567890
", "description": "", "primaryCategoryId": "178115", "aspects": [ { "name": "12345678901234567890123456789012345678901234567890", "values": ["n/a"] }, { "name": "n/a", "values": ["12345678901234567890123456789012345678901234567
89012345678901234567890
"] } ], "imageUrl": "", "brand": "New", "upc": ["123"], "mpn": ["!@#$%"] } }

A Location HTTP header is returned with the full endpoint to retrieve status of the catalog change request. The unique catalog change request identifier is appended to the end of the endpoint, and this identifier should be captured and stored.

GET https://api.ebay.com/commerce/catalog/v1_beta/change_request/5ba1375cfd5ea95c1a3c72c9

Note: This request ID value is specific to the user, so the one you receive will be different.

Call getChangeRequest to get the status of the product creation request. The status should be REJECTED, and the multiple reasons for the rejection should also be returned in the response.

GET https://api.ebay.com/commerce/catalog/v1_beta/
change_request/5ba1375cfd5ea95c1a3c72c9

Response payload:

{
"changeRequestId": "5ba1375cfd5ea95c1a3c72c9",
  "changeRequestType": "PRODUCT_CREATION",
  "changeRequestStatus": "REJECTED",
  "creationDate": "2018-09-18T17:35:24.830Z",
  "reasonForChangeRequest": "Request to add new product",
  "resolutionDate": "2018-09-18T17:35:24.898Z",
  "suggestedProduct": {
    "title": "1234567890123456789012345678901234567890123456789012
345678901234567890123456789012345678901234567890", "primaryCategoryId": "178115", "aspects": [ { "name": "12345678901234567890123456789012345678901234567890", "values": [ "n/a" ] }, { "name": "n/a", "values": [ "123456789012345678901234567890123456789012345678901234567
8901234567890" ] } ], "brand": "New", "mpn": [ "!@#$%" ], "upc": [ "123" ] }, "processResolution": { "productHref": null, "violations": [ { "violationCode": "3802", "reason": "Include at least 1 photos. Up to 12 photos are allowed.", "productAttribute": { "name": "GENERAL" } }, { "violationCode": "3001", "reason": "Title length, 100, is not within the required range
of 1-80 characters.
", "productAttribute": { "values": [ "1234567890123456789012345678901234567890123456789012345678901234567
890123456789012345678901234567890" ], "name": "TITLE" } }, { "violationCode": "3301", "reason": "Invalid MPN !@#$%. Enter a valid MPN.", "productAttribute": { "values": [ "!@#$%" ], "name": "MPN" } }, { "violationCode": "3201", "reason": "UPC has an invalid value of 123. Enter a valid value
and try again.
", "productAttribute": { "values": [ "123" ], "name": "UPC" } }, { "violationCode": "3401", "reason": "Invalid Brand New. Enter a valid Brand.", "productAttribute": { "values": [ "New" ], "name": "BRAND" } }, { "violationCode": "3701", "reason": "Product specific name length is {ASPECT_LENGTH}
characters. This is not within the required range of 1-45 characters.
", "productAttribute": { "values": [ "12345678901234567890123456789012345678901234567890" ], "name": "ASPECT_NAME" } }, { "violationCode": "3902", "reason": "Product specific name length can only be 45
characters or less.
", "aspectsValues": { "aspectName": "n/a", "values": [ "123456789012345678901234567890123456789012345678901234567
8901234567890" ] } } ] } }

Note: When a test change request is rejected, all possible violations are returned. In real world use, only the violations that apply to this request would be returned.

Other Ways to Trigger REJECTION Status for New Product Request

In addition to the catalog change request errors in the two previous examples that trigger rejections, the following data will also trigger catalog change request rejections:

  • A brand value is specified in the catalog change request, but a corresponding mpn value is missing.
  • The same values are used for brand and the corresponding mpn.

Updating a catalog product in a test category

Use the createChangeRequest method to make a request to revise an existing catalog product in one of the test categories. You can use the preceding PRODUCT_CREATION examples to test for the outcomes in those examples by adjusting your createChangeRequest call as follows:

  • Set the value of the changeRequestType field to PRODUCT_UPDATE.
  • Include the suggestedProduct.epid field, set to the value returned by the getChangeRequest call in the processResolution.epid field of an approved new product change request.
  • Include the suggestedProduct.version field, set to the value returned by the getChangeRequest call in the suggestedProduct.version field of an approved new product change request.

The following tables contain additional examples that demonstrate requests ending in the UNDER_REVIEW and UNDER_EXTENDED_ REVIEW values of the changeRequestStatus field. The createChangeRequest call submits the ePID of a product previously created with a successful PRODUCT_CREATION request.

Note: Red text in the following examples indicates significant values to use in a request or to note in a response.

Product update request is under review

Call createChangeRequest to make a product update request that is under review.

POST https://api.ebay.com/commerce/catalog/v1_beta/change_request

Request payload:

{
  "changeRequestType": "PRODUCT_UPDATE",
  "reasonForChangeRequest": "Request to update a product",

  "suggestedProduct": {
    "title": "Appeal is being reviewed by agent",
    "description": "This Space Grey iPhone 20 comes with 256GB
of storage, and can be used on any carrier network in the US.",
    "primaryCategoryId": "178114",
     "version": "1",
  "epid": "3020418775",
    "aspects": [
        {
          "name": "Model",
          "values": ["iPhone 20"]
        }
    ],
    "imageUrl": "https://i.ebayimg.com/00/6.JPG?set_id=89040003C1C1",
    "brand": "Apple",
    "upc": ["0745577656433"],
    "mpn": ["MD295LL\/A"]
  }
}

After some time, call getChangeRequest to demonstrate that the request is in UNDER_REVIEW status.

GET https://api.ebay.com/commerce/catalog/v1_beta/change_request/5b243489fae61a2960b852b6

Response payload:

{
    "changeRequestId": "5b243489fae61a2960b852b6",
    "changeRequestType": "PRODUCT_UPDATE",
    "changeRequestStatus": "UNDER_REVIEW",
    "creationDate": "2018-06-15T21:50:01.422Z",
    "reasonForChangeRequest": "Request to update a product",
    "resolutionDate": "2018-06-15T21:50:01.568Z",
    "suggestedProduct": {
        "epid": "3020418775",
        "version": "1",
        "title": "Appeal is being reviewed by agent",
        "description": "This Space Grey iPhone 20 comes with 256GB
of storage, and can be used on any carrier network in the US.",
        "primaryCategoryId": "178114",
        "aspects": [
            {
                "name": "Model",
                "values": [
                    "iPhone 20"
                ]
            }
        ],
        "imageUrl": "https://i.ebayimg.com/00/6.JPG?set_id=89040003C1C1",
        "brand": "Apple",
        "mpn": [
            "MD295LL/A"
        ],
        "upc": [
            "0745577656433"
        ]
    },
    "processResolution": {}
}

Product update request is under extended review

Call createChangeRequest to make a product update request that is under extended review.

POST https://api.ebay.com/commerce/catalog/v1_beta/change_request

Request payload:

{
  "changeRequestType": "PRODUCT_UPDATE",
  "reasonForChangeRequest": "Request to update a  product",
  "suggestedProduct": {
    "aspects": [

    ],
    "title": "How to optimize for free shipping",
    "description": "This Space Grey iPhone 20 comes with 256GB
of storage, and can be used on any carrier network in the US.",
    "version": "2",

    "mpn": [
      "MD295LL/A"
    ],
    "upc": [
      "0745577656433"
    ],
    "brand": "Apple",
    "epid": "26020409399",

      "imageUrl": "https://i.ebayimg.com/00/6.JPG?set_id=89040003C1C1",

    "primaryCategoryId": "178114"
  }
}

After some time, call getChangeRequest to demonstrate that the request is in UNDER_EXTENDED_REVIEW status.

GET https://api.ebay.com/commerce/catalog/v1_beta/change_request/5b24369e8702d13a07161d25

Response payload:

{
    "changeRequestId": "5b24369e8702d13a07161d25",
    "changeRequestType": "PRODUCT_UPDATE",
    "changeRequestStatus": "UNDER_EXTENDED_REVIEW",
    "creationDate": "2018-06-15T21:58:54.501Z",
    "reasonForChangeRequest": "Request to update a  product",
    "resolutionDate": "2018-06-15T21:58:54.755Z",
    "suggestedProduct": {
        "epid": "26020409399",
        "version": "2",
        "title": "How to optimize for free shipping",
        "description": "This Space Grey iPhone 20 comes with 256GB
of storage, and can be used on any carrier network in the US.",
        "primaryCategoryId": "178114",
        "imageUrl": "https://i.ebayimg.com/00/6.JPG?set_id=89040003C1C1",
        "brand": "Apple",
        "mpn": [
            "MD295LL/A"
        ],
        "upc": [
            "0745577656433"
        ]
    },
    "processResolution": {}
}

Listing against a new catalog product

Once you have created a new catalog product in one of the test categories, you can use either the Inventory API methods or the Trading API's AddItem call to create a listing that is associated with this new catalog product. The following two sections summarize the process for each API.

Listing against a new catalog product with Inventory API

The process for using the Inventory API to create a new listing associated with a catalog product is covered under Creating listings with a catalog product using the Inventory API. This assumes you have already created an inventory location using the createInventoryLocation call.

To list a product in a test category:

  1. Use the createOrReplaceInventoryItem call to create an inventory item record. Include the seller-defined stock keeping unit (SKU) identifier for the item in the call's sku parameter. The SKU value is currently required to create an inventory item. Include also the product.epid field with the ePID value of 26020409399, which identifies the new catalog product that was previously created by the APPROVED change request in test category 178114. The product could also have been created with a change request that was APPROVED_WITH_MODIFICATIONS. As long as eBay is able to match the supplied ePID value to the catalog product, all product details of the new catalog product are picked up by the inventory item record.
  2. Use the createOffer call to produce an unpublished offer of the inventory item. Include the categoryId field with the test category ID, 178114, that you previously used to create the product. This call returns the offerId field, the value of which you use for the next step.
  3. Use the publishOffer call to publish the offer as an eBay listing. Include the offerId value from the previous step as a path parameter.

Because test category 178114 is a PBSE-enforced category, listings in this category must adopt a catalog product. You can examine the Production test leaf categories for testing PBSE use cases to see which ones are PBSE-enforced and which are only PBSE-enabled. Listings of items in a PBSE-enabled category can be created without adopting a catalog product.

Listing against a new catalog product with Trading API

Use the AddItem or AddFixedPriceItem call to create a new listing in test category 178114. You include this value in the Item.PrimaryCategory.CategoryID field, along with the other fields required by the call.

Test category 178114 is a PBSE-enforced category, which indicates that listings in this category must adopt a catalog product. You must also include the ePID value of 26020409399 in the ProductListingDetails.ProductReferenceID field of the AddItem or AddFixedPriceItem call or the call will fail. The ePID 26020409399 identifies the new catalog product that was previously created by the APPROVED change request in test category 178114. The product could also have been created with a change request that was APPROVED_WITH_MODIFICATIONS.

You can examine the Production test leaf categories for testing PBSE use cases to see which ones are PBSE-enforced and which are only PBSE-enabled. Listings of items in a PBSE-enabled category can be created without adopting a catalog product.

The Trading API listing process is covered in the Creating a single-variation listing with a catalog product using the Trading API PBSE Playbook topic.

Verifying the catalog product in your listing

To verify that your new catalog product has been adopted for your listing, you can examine the listing programmatically or on the eBay website.

  • Use the Trading API's GetItem call to retrieve the details of the listed item. The ePID value should be returned in the ProductReferenceID field.
  • Go to your Seller page on My eBay and examine your active item listings. The ePID value should be in the item details.

Creating a multiple-variation listing

Each variation in a multiple-variation (or multi-SKU) listing is treated as an independent inventory item which could be listed by itself. As such, each variation should have its own seller-defined stock keeping unit (SKU) identifier, and for PBSE, each listing will be based on a different catalog product. You can create multi-SKU listings with the Inventory API or the Trading API.

Note: Currently it's not possible to provide multiple ePID or GTIN (EAN, ISBN, or UPC) values to list multiple variations in test categories. The following sections that cover creating multiple-variation listings with the Inventory and Trading APIs are not yet valid. The ePID value will be supported with test categories shortly.

Adding multiple new catalog products to a test category

Go to the Adding catalog product to test category section for details on how to add a new catalog product to test category 178114 using the createChangeRequest call. Repeat this step for each variation (SKU).

Creating a multiple-variation listing using Inventory API

Note: The steps in this section currently do not work with products in test categories. They will be usable shortly.

To list multiple variations of seller inventory in a test category:

  1. Use the createOrReplaceInventoryItem call to create an inventory item record for each variation. Include the seller-defined SKU identifier for the item in the call's sku parameter. The SKU value is required to create an inventory item. Include also the product.epid field for each variation, but do NOT use an ePID value. Currently, the variation's ePID value is not supported for listing multiple variations; instead, provide a valid GTIN value (EAN, ISBN, or UPC) in the epid field. The ePID value will be supported later in Summer 2018.
  2. Use the createOrReplaceInventoryItemGroup call to associate multiple inventory items together so they will appear as variations in the same listing. The seller must define a unique identifier for the group and submit it in the call's inventoryItemGroupKey parameter. This key cannot be changed once the inventory item group has been created. Use the variantSKUs container to specify the all of the inventory items/variations that will be part of the group.
  3. Use the createOffer call to produce an unpublished offer of each inventory item (variation) in the group. Include the categoryId field with the test category ID 178114 that you previously used to create each product. Repeat this step for each inventory item in the group.
  4. Use the publishOfferByInventoryItemGroup call to simultaneously publish the offers created for all variations in the group as a single multi-SKU listing. You identify the group using the seller's previously created inventoryItemGroupKey.

Creating a multiple-variation listing using Trading API

Note: The steps in this section currently do not work with products in test categories. They will be usable shortly.

The AddFixedPriceItem call (AddItem call doesn't support variations) is used to create a new multiple-variation listing that is associated with a catalog product. This process is covered in the Creating a multiple-variation listing with a catalog product using the Trading API section of the Phase 2 recommended workflows using Trading API PBSE Playbook topic.

Viewing a successfully created multiple-variation listing

Use the listingId that is returned in the publishOfferByInventoryItemGroup method of the Inventory API, or the ItemID that is returned in the AddFixedPriceItem call of the Trading API to view the results of the listing

In the Trading API, you could call GetItem to verify that each variation was created correctly with the right ePID value. In the GetItem request payload, you'd set the following parameters:

In the response, verify that each variation has the correct information, including the ePID value that is found in the Variation.VariationProductListingDetails container.

In the Inventory API, you can call getOffer to verify listing-level data like price or availableQuantity. The listingId value returned in that call should be the same for all offers in that inventory item group, and the returned status value should be PUBLISHED. The getInventoryItem method can be called to verify variation-level data that is found in the product container, including the ePID value, and the groupIds value should be returned, and the same value for all inventory items in the inventory item group.

Listing bundles and modified or non-domestic items with instance specifics

When creating special listings like bundles, modified items, and foreign items you will still need to associate them with a catalog product. Follow the flow in the table below to create a new product-based listing with instance specifics in an eBay test category. This process is covered in the Associating catalog products to special listings section of the playbook.

The instance aspects to include in special listings like Custom Bundle, Bundle Description, Modified Item, Modification Description, Non-Domestic Product, and Applicable Regions are described in the table below.

Custom Bundle

Bundle Description

Modified Item

Modification Description

Non-Domestic Product

Applicable Regions

Indicate if the main item is sold with complementary items. For example: a body camera with a lens and camera case.

Describe exactly what's included in your bundle.For example, "This camera body includes an 18-55mm lens and black Pelican carry case."

Indicate if the item has been modified in some way. For example, an autographed book or a customized cell phone case.

Describe exactly how the item has been modified. For example, "This iPhone has been professionally gold plated with 24 karat gold. The phone is being paid directly from Apple and opened for gold plating purposes. "

Indicate if the product is designed for use in a region other than where it is listed. For example, if selling a UK hairdryer in the US (different voltage and outlet connection).

Indicate in which region (s) the product is designed to be used, separating each region with a comma. For example, UK, Rep. Ireland, Hong Kong.

If you're working with the Trading API, use the GetCategorySpecifics call to get instance specific aspects for one of the test categories provided here. This will reveal which aspects are allowed for the given category and which aspects are instance aspects (aspects that can be provided for a listing but not for a catalog product). The AspectUsage fields in the NameRecommendation.ValidationRules container can be accompanied by a MaxValueLength field. If you're using the Taxonomy API, call the getItemAspectsForCategory method and pass the test category ID in the category_id query parameter.

Using standalone catalog change request web flows

Third-party developers can use eBay's stand-alone web pages to enable sellers to file requests to add or update products in the eBay catalog and view the status of these requests, without building their own user interface on top of the Catalog API.

The standalone catalog change request web flows will be available for the production test categories. For more information on setting this up, please see the Making a catalog change request using stand-alone web flows section in the Making a catalog change request PBSE Playbook topic.

Production test leaf categories for testing PBSE use cases

The following two tables contain three sets of test categories for each eBay marketplace that supports PBSE - AU, US, UK, CA (English). For some of the test categories, PBSE is enforced and listings cannot be created without using a eBay Catalog product. For other test categories, listing with an ebay Catalog product is optional, but not required. For the remaining test categories, listing with an eBay Catalog product is not possible. Each test category has instance aspects (if applicable for the category). For the non-PBSE categories, the product aspects are not returned by the Catalog API's product_metadata methods.

Test categories for US, UK, AU

The following table contains information about Production test categories that were created on the US, UK, and Australia sites, and each test category represents an actual Production leaf category, and the actual metadata associated with that category. that it . and three category IDs that can be used to work with the test category. For example, the Category 1 test category in the first row of the table mirrors Production category 9355, but the test category IDs (and category path) are different for the three different sites. Note that Canada Production test category IDs can be found in its own table below this one.

PBSE Status (Applied to Test Category Only) (US, UK, AU) Test Category Name Production Leaf Category US Production Test Category ID US Production Test Category Path UK Production Test Category ID UK Production Test Category Path AU Production Test Category ID AU Test Category Path
PBSE-enforced Category 1 Mobile Phones (9355) 178114 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 1 (178114) 178245 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 1 (178245) 178376 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 1 (178376)
PBSE-enforced Category 2 Voice-Enabled Smart Assistants (184435) 178115 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 2 (178115) 178246 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 2 (178246) 178377 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 2 (178377)
PBSE-enforced Category 3 Internet & Media Streamers (168058) 178116 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 3 (178116) 178247 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 3 (178247) 178378 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 3 (178378)
PBSE-enforced Category 4 TVs (11071) 178117 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 4 (178117) 178248 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 4 (178248) 178379 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 4 (178379)
PBSE-enforced Category 5 Home Appliances (20710) > Heating, Cooling & Air (69197) > Humidifiers (71240) 178118 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 5 (178118) 178249 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 5 (178249) 178380 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 5 (178380)
PBSE-enforced Category 6 Programmable Thermostats (115949) 178119 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 6 (178119) 178250 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 6 (178250) 178381 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 6 (178381)
PBSE-enforced Category 7 Portable Fans (20612) 178120 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 7 (178120) 178251 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 7 (178251) 178382 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 7 (178382)
PBSE-enforced Category 8 Portable Heaters (20613) 178121 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 8 (178121) 178252 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 8 (178252) 178383 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 8 (178383)
PBSE-enforced Category 9 Home Appliances (20710) > Small Kitchen Appliances (20667) > Blenders (Countertop) (133704) 178122 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 9 (178122) 178253 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 9 (178253) 178384 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 9 (178384)
PBSE-enforced Category 10 Microwave Ovens (150140) 178123 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 10 (178123) 178254 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 10 (178254) 178385 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 10 (178385)
PBSE-enabled Category 11 Elliptical Trainers (72602) 178124 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 11 (178124) 178255 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 11 (178255) 178386 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 11 (178386)
PBSE-enabled Category 12 Exercise Bikes (58102) 178125 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 12 (178125) 178256 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 12 (178256) 178387 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 12 (178387)
PBSE-enabled Category 13 Gliders (58105) 178126 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 13 (178126) 178257 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 13 (178257) 178388 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 13 (178388)
PBSE-enabled Category 14 Machine Parts & Accessories (179797) 178127 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 14 (178127) 178258 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 14 (178258) 178389 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 14 (178389)
PBSE-enabled Category 15 Other (28063) 178128 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 15 (178128) 178259 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 15 (178259) 178390 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 15 (178390)
PBSE-enabled Category 16 Rowing Machines (28060) 178129 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 16 (178129) 178260 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 16 (178260) 178391 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 16 (178391)
PBSE-enabled Category 17 Ski Machines (28061) 178130 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 17 (178130) 178261 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 17 (178261) 178392 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 17 (178392)
PBSE-enabled Category 18 Step Machines (28062) 178131 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 18 (178131) 178262 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 18 (178262) 178393 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 18 (178393)
PBSE-enabled Category 19 Treadmills (15280) 178132 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 19 (178132) 178263 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 19 (178263) 178394 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 19 (178394)
PBSE-enabled Category 20 Vibration Machines (171593) 178133 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 20 (178133) 178264 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 20 (178264) 178395 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 20 (178395)
Non-PBSE Category 21 No product specifics seeded here 178134 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 21 (178134) 178265 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 21 (178265) 178396 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 21 (178396)
Non-PBSE Category 22 No product specifics seeded here 178135 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 22 (178135) 178266 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 22 (178266) 178397 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 22 (178397)
Non-PBSE Category 23 No product specifics seeded here 178136 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 23 (178136) 178267 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 23 (178267) 178398 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 23 (178398)
Non-PBSE Category 24 No product specifics seeded here 178137 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 24 (178137) 178268 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 24 (178268) 178399 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 24 (178399)
Non-PBSE Category 25 No product specifics seeded here 178138 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > eBay Test Only (178086) > Group 2 (178113) > Category 25 (178138) 178269 Everything Else (99) > Test Auctions (14112) > eBay Test Only (178217) > Group 2 (178244) > Category 25 (178269) 178400 Lots More... (99) > Test Auctions (14112) > eBay Test Only (178348) > Group 2 (178375) > Category 25 (178400)

Test categories for CA

Each row of the following table contains information about one test category, including the real production leaf category it represents, and the category ID that can be used to work with the test category.

PBSE Status (Applied to Test Category Only) (CA) Test Category Name Production Leaf Category CA US Production Test Category ID US Production Test Category Path
PBSE-enforced Attributes2 Cell Phones & Smartphones (9355) 37559 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > Test Category For Internal Use Only Parent Level 3 (37557) > Attributes2 (37559)
PBSE-enforced Attributes3 Voice-Enabled Smart Assistants (184435) 37560 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > Test Category For Internal Use Only Parent Level 3 (37557) > Attributes3 (37560)
PBSE-enforced Attributes4 Internet & Media Streamers (168058) 37561 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > Test Category For Internal Use Only Parent Level 3 (37557) > Attributes4 (37561)
PBSE-enforced Attributes5 TVs (11071) 37562 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > Test Category For Internal Use Only Parent Level 3 (37557) > Attributes5 (37562)
PBSE-enforced Attributes6_Test Humidifiers (71240) 37563 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > Test Category For Internal Use Only Parent Level 3 (37557) > Attributes6_Test (37563)
PBSE-enabled Attributes7 Ellipticals (72602) 37565 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > Test Category For Internal Use Only Parent Level 3 (37557) > Attributes7 (37565)
PBSE-enabled Attributes8 Exercise Bikes (58102) 37566 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > Test Category For Internal Use Only Parent Level 3 (37557) > Attributes8 (37566)
PBSE-enabled Attributes9 Gliders (58105) 37567 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > Test Category For Internal Use Only Parent Level 3 (37557) > Attributes9 (37567)
PBSE-enabled Attributes10 Machine Parts & Accessories (179797) 37568 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > Test Category For Internal Use Only Parent Level 3 (37557) > Attributes10 (37568)
Non-PBSE Attributes11 No product specifics seeded here 38338 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > Test Category For Internal Use Only Parent Level 3 (37557) > Attributes11 (38338)
Non-PBSE Attributes12 No product specifics seeded here 38339 Everything Else (99) > Test Category For Internal Use Only Parent Level 2 (14112) > Test Category For Internal Use Only Parent Level 3 (37557) > Attributes12 (38339)