Can HumDay connect to VTEX Catalog?

Yes. HumDay reads VTEX Catalog's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 162 operations are documented.

Do I need to write code to automate VTEX Catalog?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your VTEX Catalog account.

What can HumDay do in VTEX Catalog?

93 of the 162 documented operations change something in VTEX Catalog, and 69 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my VTEX Catalog account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to VTEX Catalog is held behind that approval.

Automate VTEX Catalog

HumDay reads VTEX Catalog’s own published API description and derives 162 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What VTEX Catalog is

> Check the new [Catalog onboarding guide](https://developers.vtex.com/docs/guides/catalog-overview). We created this guide to improve the onboarding experience for developers at VTEX. It assembles all documentation on our Developer Portal about Catalog and is organized by focusing on the developer's journey. Methods for collecting product/SKU catalog data, categories, brands and other information

API host: vtex.local

What HumDay can do in VTEX Catalog

93 documented operations change something in VTEX Catalog. The 69 most useful are listed here.

POSTCreate Brand/api/catalog/pvt/brand
POSTCreate Product with Category and Brand/api/catalog/pvt/product
POSTCreate Category/api/catalog/pvt/category
POSTCreate Supplier/api/catalog/pvt/supplier
POSTCreate attachment/api/catalog/pvt/attachment
POSTCreate Collection/api/catalog/pvt/collection/
POSTCreate Seller/api/catalog_system/pvt/seller
POSTCreate SKU Complement/api/catalog/pvt/skucomplement
POSTCreate Specification/api/catalog/pvt/specification
POSTCreate SKU Service Type/api/catalog/pvt/skuservicetype
POSTCreate SKU Service Value/api/catalog/pvt/skuservicevalue
POSTCreate SKU/api/catalog/pvt/stockkeepingunit
POSTCreate Specification Group/api/catalog/pvt/specificationgroup
POSTCreate Specification Value/api/catalog/pvt/specificationvalue
POSTCreate SKU Kit/api/catalog/pvt/stockkeepingunitkit
DELETEDelete All SKU Files/api/catalog/pvt/stockkeepingunit/{skuId}/file
POSTCreate SKU File/api/catalog/pvt/stockkeepingunit/{skuId}/file
POSTCreate Specification Field/api/catalog_system/pvt/specification/field
POSTCreate Specification Field Value/api/catalog_system/pvt/specification/fieldValue
POSTRetrieve SKU ID list by Reference ID list/api/catalog_system/pub/sku/stockkeepingunitidsbyrefids
POSTAdd products to Collection by imported file/api/catalog/pvt/collection/{collectionId}/stockkeepingunit/importinsert
POSTAssociate SKU Service/api/catalog/pvt/skuservice
PUTUpdate Seller/api/catalog_system/pvt/seller
DELETEDissociate attachments and SKUs/api/catalog/pvt/skuattachment
POSTAssociate SKU Attachment/api/catalog/pvt/skuattachment
DELETEDelete SKU Kit by SKU ID or Parent SKU ID/api/catalog/pvt/stockkeepingunitkit
DELETEDissociate Attachment by Attachment ID or SKU Service Type ID/api/catalog/pvt/skuservicetypeattachment
POSTAssociate SKU Service Attachment/api/catalog/pvt/skuservicetypeattachment
POSTChange Notification with SKU ID/api/catalog_system/pvt/skuseller/changenotification/{skuId}
PUTCopy Files from an SKU to another SKU/api/catalog/pvt/stockkeepingunit/copy/{skuIdfrom}/{skuIdto}/file/
PUTUpdate Specification Field/api/catalog_system/pvt/specification/field
DELETEDelete Non Structured Specification by SKU ID/api/catalog/pvt/specification/nonstructured
DELETEDelete Brand/api/catalog/pvt/brand/{brandId}
PUTUpdate Brand/api/catalog/pvt/brand/{brandId}
POSTAssociate attachments to an SKU/api/catalog_system/pvt/sku/associateattachments
PUTUpdate Specification Field Value/api/catalog_system/pvt/specification/fieldValue
PUTUpdate Product/api/catalog/pvt/product/{productId}
PUTUpdate Category/api/catalog/pvt/category/{categoryId}
DELETEDelete Supplier/api/catalog/pvt/supplier/{supplierId}
PUTUpdate Supplier/api/catalog/pvt/supplier/{supplierId}
PUTUpdate SKU/api/catalog/pvt/stockkeepingunit/{skuId}
DELETEDelete attachment/api/catalog/pvt/attachment/{attachmentid}
PUTUpdate attachment/api/catalog/pvt/attachment/{attachmentid}
DELETEDissociate SKU Service/api/catalog/pvt/skuservice/{skuServiceId}
PUTUpdate SKU Service/api/catalog/pvt/skuservice/{skuServiceId}
DELETEDelete SKU Kit by KitId/api/catalog/pvt/stockkeepingunitkit/{kitId}
PUTUpdate Specification Group/api/catalog/pvt/specificationgroup/{groupId}
POSTCreate SKU EAN/api/catalog/pvt/stockkeepingunit/{skuId}/ean/{ean}
DELETEDelete SKU Complement by SKU Complement ID/api/catalog/pvt/skucomplement/{skuComplementId}
PUTUpdate Specification/api/catalog/pvt/specification/{specificationId}
DELETEDelete SKU Service Type/api/catalog/pvt/skuservicetype/{skuServiceTypeId}
PUTUpdate SKU Service Type/api/catalog/pvt/skuservicetype/{skuServiceTypeId}
DELETEDelete SKU Service Value/api/catalog/pvt/skuservicevalue/{skuServiceValueId}
PUTUpdate SKU Service Value/api/catalog/pvt/skuservicevalue/{skuServiceValueId}
POSTRemove products from Collection by imported file/api/catalog/pvt/collection/{collectionId}/stockkeepingunit/importexclude
DELETEDelete SKU Image File/api/catalog/pvt/stockkeepingunit/{skuId}/file/{skuFileId}
PUTUpdate SKU File/api/catalog/pvt/stockkeepingunit/{skuId}/file/{skuFileId}
PUTUpdate Specification Value/api/catalog/pvt/specificationvalue/{specificationValueId}
DELETEDelete SKU Attachment by Attachment Association ID/api/catalog/pvt/skuattachment/{skuAttachmentAssociationId}
POSTAdd Similar Category/api/catalog/pvt/product/{productId}/similarcategory/{categoryId}
DELETEDelete all SKU EAN values/api/catalog/pvt/stockkeepingunit/{skuId}/ean
DELETEDelete Non Structured Specification/api/catalog/pvt/specification/nonstructured/{Id}
DELETEDelete all Product Specifications by Product ID/api/catalog/pvt/product/{productId}/specification
POSTAssociate Product Specification/api/catalog/pvt/product/{productId}/specification
DELETEDissociate Attachment from SKU Service Type/api/catalog/pvt/skuservicetypeattachment/{skuServiceTypeAttachmentId}
POSTChange Notification with Seller ID and Seller SKU ID/api/catalog_system/pvt/skuseller/changenotification/{sellerId}/{sellerSkuId}
PUTAssociate product specification using specification name and group name/api/catalog/pvt/product/{productId}/specificationvalue
DELETEDelete all SKU Specifications/api/catalog/pvt/stockkeepingunit/{skuId}/specification
POSTAssociate SKU Specification/api/catalog/pvt/stockkeepingunit/{skuId}/specification

What HumDay can read from VTEX Catalog

These are the operations a schedule or a trigger can watch.

GETGet Brand List Per Page/api/catalog_system/pvt/brand/pagedlist
GETGet Sales Channel List/api/catalog_system/pvt/saleschannel/list
GETGet SKU Files/api/catalog/pvt/stockkeepingunit/{skuId}/file
GETGet Brand List/api/catalog_system/pvt/brand/list
GETGet Seller List/api/catalog_system/pvt/seller/list
GETGet All Collections/api/catalog_system/pvt/collection/search
GETList all SKU IDs/api/catalog_system/pvt/sku/stockkeepingunitids
GETGet all commercial conditions/api/catalog_system/pvt/commercialcondition/list
GETList all SKUs of a Trade Policy/api/catalog_system/pvt/sku/stockkeepingunitidsbysaleschannel
GETGet Sales Channel by ID/api/catalog_system/pub/saleschannel/{salesChannelId}
GETGet all attachments/api/catalog/pvt/attachments
GETGet Gift List/api/addon/pvt/giftlist/get/{listId}
GETGet SKU by RefId/api/catalog/pvt/stockkeepingunit
GETGet SKU Kit by SKU ID or Parent SKU ID/api/catalog/pvt/stockkeepingunitkit
GETImport Collection file example/api/catalog/pvt/collection/stockkeepingunit/importfileexample
GETGet Collections by search terms/api/catalog_system/pvt/collection/search/{searchTerms}
GETGet All Inactive Collections/api/catalog/pvt/collection/inactive
GETList Specification Group by Category/api/catalog_system/pvt/specification/groupbycategory/{categoryId}
GETGet SKU list by Product ID/api/catalog_system/pvt/sku/stockkeepingunitByProductId/{productId}
GETGet Non Structured Specification by SKU ID/api/catalog/pvt/specification/nonstructured
GETGet Brand and context/api/catalog/pvt/brand/{brandId}
GETGet Product by ID/api/catalog/pvt/product/{productId}
GETGet Product and SKU IDs/api/catalog_system/pvt/products/GetProductAndSkuIds
GETGet Category by ID/api/catalog/pvt/category/{categoryId}
GETGet Brand/api/catalog_system/pvt/brand/{brandId}
GETGet Seller by ID/api/catalog_system/pvt/seller/{sellerId}
GETGet SKU/api/catalog/pvt/stockkeepingunit/{skuId}
GETGet Seller by ID/api/catalog_system/pvt/sellers/{sellerId}
GETGet attachment/api/catalog/pvt/attachment/{attachmentid}
GETGet SKU Service/api/catalog/pvt/skuservice/{skuServiceId}
GETGet SKU Kit/api/catalog/pvt/stockkeepingunitkit/{kitId}

How automating VTEX Catalog works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live VTEX Catalog account.
Grant access, then go live. You approve the specific VTEX Catalog operations it may use — and only those.

Automate VTEX Catalog with these

Questions about VTEX Catalog automation

Can HumDay connect to VTEX Catalog?: Yes. HumDay reads VTEX Catalog's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 162 operations are documented.
Do I need to write code to automate VTEX Catalog?: No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your VTEX Catalog account.
What can HumDay do in VTEX Catalog?: 93 of the 162 documented operations change something in VTEX Catalog, and 69 read from it. HumDay only ever uses the specific operations your approved contract needs.
Is my VTEX Catalog account safe?: Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to VTEX Catalog is held behind that approval.

Where this came from

The operations above are read from a published API description for VTEX Catalog at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - Catalog API.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-03.