Alternative API requests

As you may have noticed, many catalog API requests use VTEX IDs in order to create and update values. Fields like BrandId, FieldId, FieldValueId, GroupId and CategoryId.

While it is important to keep track of these IDs, there are some alternative endpoints that do not require them for performing some tasks.

Create product using brand name and category path

Create product API endpoint

Example body:


_16{
_16    "Name": "Test Product",
_16    "CategoryPath": "Storage/Hard Drive",
_16    "BrandName": "Sample Brand",
_16    "RefId": "310117069123",
_16    "Title": "Browser Title for this product",
_16    "LinkId": "test-product",
_16    "Description": "This is a cool product",
_16    "ReleaseDate": "2019-01-01T00:00:00",
_16    "IsVisible": true,
_16    "IsActive": true,
_16    "TaxCode": "",
_16    "MetaTagDescription": "tag test",
_16    "ShowWithoutStock": true,
_16    "Score": 1
_16}

Create product specification using field, group names

API request: Associate product specification using specification and group names

Example body


_10{
_10    "FieldName": "TesteAPI",
_10    "GroupName": "TestGroup",
_10    "RootLevelSpecification": true,
_10    "FieldValues": [
_10        "Value123"
_10        ]
_10}