VTEX SKU Approval Settings API

The SKU Approval Settings API from VTEX — 5 operation(s) for sku approval settings.

Operations 8

GET /suggestions/configuration/autoapproval/toggle VTex Get autoApprove Status in Account Settings #
PUT /suggestions/configuration/autoapproval/toggle VTex Activate autoApprove in Marketplace's Account #
GET /suggestions/configuration VTex Get Account's Approval Settings #
PUT /suggestions/configuration VTex Save Account's Approval Settings #
GET /suggestions/configuration/account/config VTex Get Account's Matcher Settings #
GET /suggestions/configuration/seller/{sellerId} VTex Get Seller's Approval Settings #
PUT /suggestions/configuration/seller/{sellerId} VTex Save Seller's Approval Settings #
PUT /suggestions/configuration/autoapproval/toggle/seller/{sellerId} VTex Activate autoApprove Setting for a Seller #

Documentation

📖
Documentation
https://developers.vtex.com/docs/guides/how-the-integration-protocol-between-vtex-and-antifraud-companies-works
📖
Documentation
https://developers.vtex.com/docs/guides/bulk-import-buyer-organizations-spreadsheet
📖
Documentation
https://developers.vtex.com/docs/guides/catalog-api-seller-portal-overview
📖
Documentation
https://developers.vtex.com/docs/guides/catalog-overview
📖
Documentation
https://developers.vtex.com/docs/guides/checkout-overview
📖
Documentation
https://help.vtex.com/en/tutorial/customer-credit-overview--1uIqTjWxIIIEW0COMg4uE0
📖
Documentation
https://help.vtex.com/en/tutorial/data-subject-rights--6imchxTx09icupKMbzHVIM
📖
Documentation
https://developers.vtex.com/docs/api-reference/do-api
📖
Documentation
https://developers.vtex.com/docs/guides/managing-vtex-gift-cards
📖
Documentation
https://developers.vtex.com/docs/guides/gift-card-integration-guide
📖
Documentation
https://developers.vtex.com/docs/guides/faststore/headless-cms-overview
📖
Documentation
https://developers.vtex.com/docs/api-reference/vtex-id-api
📖
Documentation
https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG
📖
Documentation
https://developers.vtex.com/docs/apps/vtex.search@1.0.8
📖
Documentation
https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj
📖
Documentation
https://developers.vtex.com/docs/guides/search-overview
📖
Documentation
https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3
📖
Documentation
https://developers.vtex.com/docs/guides/fulfillment
📖
Documentation
https://developers.vtex.com/docs/guides/marketplace-overview
📖
Documentation
https://developers.vtex.com/updates/release-notes/marketplace-protocol-documentation-update
📖
Documentation
https://developers.vtex.com/docs/guides/external-marketplace-integration-guide
📖
Documentation
https://developers.vtex.com/docs/guides/external-seller-integration-connector
📖
Documentation
https://developers.vtex.com/docs/guides/external-seller-integration-guide
📖
Documentation
https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw
📖
Documentation
https://help.vtex.com/en/tutorial/understanding-the-message-center--tutorials_84
📖
Documentation
https://developers.vtex.com/docs/guides/orders-overview
📖
Documentation
https://developers.vtex.com/docs/guides/changes-in-vtex-features-behavior-to-handle-pii-data
📖
Documentation
https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m
📖
Documentation
https://developers.vtex.com/docs/guides/payments-integration-guide
📖
Documentation
https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr
📖
Documentation
https://developers.vtex.com/docs/guides/vtex-io-documentation-policies
📖
Documentation
https://developers.vtex.com/docs/guides/pricing-hub
📖
Documentation
https://developers.vtex.com/docs/guides/pricing-overview
📖
Documentation
https://developers.vtex.com/docs/guides/profile-system
📖
Documentation
https://developers.vtex.com/docs/guides/promotions-overview
📖
Documentation
https://developers.vtex.com/docs/apps/vtex.reviews-and-ratings
📖
Documentation
https://developers.vtex.com/docs/guides/sent-offers-integration-guide-connectors
📖
Documentation
https://developers.vtex.com/docs/guides/sessions-system-overview
📖
Documentation
https://developers.vtex.com/docs/guides/vtex-shipping-network
📖
Documentation
https://help.vtex.com/en/tutorial/sku-bindings--1SmrVgNwjJX17hdqwLa0TX
📖
Documentation
https://developers.vtex.com/docs/guides/subscriptions
📖
Documentation
https://developers.vtex.com/docs/apps/vtex.search/suggestions
📖
Documentation
https://developers.vtex.com/docs/guides/vtex-tracking

Specifications

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/vtex-sku-approval-settings-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

vtex-sku-approval-settings-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: VTex Suggestions SKU Approval Settings API
  description: "\nThe **Marketplace API** enables marketplaces and sellers hosted on VTEX to perform their collaborative operations.  \n\n>⚠️ The marketplace must [create an appKey and appToken](https://developers.vtex.com/docs/guides/getting-started-authentication) for each non-VTEX seller that will use this API.\n\n## Index\n\n### Notification\n\nEndpoints used by sellers to notify marketplaces that the price or inventory language has changed for one of their SKUs.\n\n`POST` [Notify marketplace of price update](https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/notificator/-sellerId-/changenotification/-skuId-/price)\n\n`POST` [Notify marketplace of inventory update](https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/notificator/-sellerId-/changenotification/-skuId-/inventory)\n\n\n### Suggestions\n\n#### Get Suggestions\n\nSearch and filter all suggestions using specific criteria.\n\n`GET` [Get all SKU Suggestions](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#get-/suggestions)\n\n`GET` [Get SKU Suggestion by ID](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#get-/suggestions/-sellerId-/-sellerSkuId-)\n\n\n#### Manage Suggestions\n\nSend or delete SKU suggestions from the seller to marketplace.\n\n`PUT` [Send SKU Suggestion](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-)\n\n`DELETE` [Delete SKU Suggestion](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#delete-/suggestions/-sellerId-/-sellerSkuId-)\n\n\n#### Get Versions\n\nSearch and filter all versions of suggestions, using specific criteria.\n\n`GET` [Get all versions](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#get-/suggestions/-sellerId-/-sellerskuid-/versions)\n\n`GET` [Get version by ID](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#get-/suggestions/-sellerId-/-sellerskuid-/versions/-version-)\n\n\n#### Match Received SKUs\n\nMatch SKU suggestions received in the marketplace.\n\n`PUT` [Match Received SKUs individually](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerskuid-/versions/-version-/matches/-matchid-)\n\n`PUT` [Match Multiple Received SKUs](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/matches/action/-actionName-)\n\n\n#### SKU Approval Settings\n\nAllows marketplaces to configure rules for automatically and manually approving SKUs received from sellers.\n\n`GET`[Get autoApprove Status in Account Settings](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#get-/suggestions/configuration/autoapproval/toggle)  \n\n`PUT`[Activate autoApprove in Marketplace's Account](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/configuration/autoapproval/toggle)  \n\n`GET`[Get Account's Approval Settings](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#get-/suggestions/configuration)\n\n`PUT`[Save Account's Approval Settings](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/configuration)\n\n`GET`[Get Seller's Approval Settings](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#get-/suggestions/configuration/seller/-sellerId-)\n\n`PUT`[Save Seller's Approval Settings](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/configuration/seller/-sellerId-)\n\n`PUT`[Activate autoApprove Setting for a Seller](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/configuration/autoapproval/toggle/seller/-sellerId-)   \n\n\n### Matched Offers\n\nOffers are seller products and SKUs that were sent to the marketplace, and already have their price and inventory level configured.\n\n`GET`[Get Matched Offers List](https://developers.vtex.com/docs/api-reference/marketplace-apis#get-/offer-manager/pvt/offers)\n\n`GET`[Get Matched Offer's Data by SKU ID](https://developers.vtex.com/docs/api-reference/marketplace-apis#get-/offer-manager/pvt/product/-productId-/sku/-skuId-)  \n\n`GET`[Get Matched Offer's Data by Product ID](https://developers.vtex.com/docs/api-reference/marketplace-apis#get-/offer-manager/pvt/product/-productId-)\n"
  contact: {}
  version: '1.0'
servers:
- url: https://api.vtex.com/{accountName}
  description: Suggestions Server URL.
  variables:
    accountName:
      description: Name of the VTEX account. Used as part of the URL.
      default: apiexamples
tags:
- name: SKU Approval Settings
paths:
  /suggestions/configuration/autoapproval/toggle:
    get:
      tags:
      - SKU Approval Settings
      summary: VTex Get autoApprove Status in Account Settings
      description: "This endpoint can be used to check whether the autoapprove setting is active or not, for a specific seller. \n\nIf the response is `true`, the autoapprove setting is active. If the response is `false`, it is inactive."
      operationId: GetautoApprovevaluefromconfig
      parameters:
      - name: sellerId
        in: query
        description: A string that identifies the seller in the marketplace. This ID must be created by the marketplace.
        required: true
        style: form
        schema:
          type: string
          default: seller123
      - name: accountName
        in: path
        required: true
        description: Name of the VTEX account that belongs to the marketplace. All data extracted, and changes added will be posted into this account.
        schema:
          type: string
          default: apiexamples
      - name: Accept
        in: header
        description: HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      - name: Content-Type
        in: header
        description: Describes the type of the content being sent.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object
                properties:
                  Enabled:
                    type: boolean
                    description: If the auto-approve setting is active for a given seller (`true`) or not (`false`).
              example:
                Enabled: false
      deprecated: false
    put:
      tags:
      - SKU Approval Settings
      summary: VTex Activate autoApprove in Marketplace's Account
      description: "This endpoint enables the autoapprove rule to a marketplace's whole Received SKUs module. Once enabling the rule, received SKUs will be automatically approved on your store, regardless of the seller. \n\n For the autoapprove rule to work as expected, the approval [Matcher score](https://help.vtex.com/en/tutorial/entendendo-a-pontuacao-do-vtex-matcher--tutorials_424) should be set up as 80 (default value), but you can configure a different number through the field `Score` in [Save Account's Approval Settings](https://developers.vtex.com/vtex-rest-api/reference/saveaccountconfig)."
      operationId: Saveautoapproveforaccount
      parameters:
      - name: accountName
        in: path
        required: true
        description: Name of the VTEX account that belongs to the marketplace. All data extracted, and changes added will be posted into this account.
        schema:
          type: string
          default: apiexamples
      - name: Accept
        in: header
        description: HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      - name: Content-Type
        in: header
        description: Describes the type of the content being sent.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      requestBody:
        description: ''
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SaveautoapproveforaccountRequest'
            example:
              Enabled: true
        required: true
      responses:
        '200':
          description: OK
          headers: {}
          content:
            application/json:
              schema:
                type: object
                properties:
                  Enabled:
                    type: boolean
                    description: If the auto-approve setting is active (`true`) or not (`false`).
              example:
                Enabled: false
      deprecated: false
  /suggestions/configuration:
    get:
      tags:
      - SKU Approval Settings
      summary: VTex Get Account's Approval Settings
      description: "This endpoint retrieves the current approval settings of a marketplace's Received SKUs module. Its response includes: \n\n- `Score`: Matcher scores for approving and rejecting SKUs received from sellers. \n\n- `Matchers`: All Matchers configured on the marketplace, and their respective details. \n\n- `SpecificationsMapping`: Mapping of product and SKU specifications, per seller. \n\n- `MatchFlux`: This field determines the type of approval configuration applied to SKUs received from a seller. \n\nThe possible values include: \n\n-`default`, where the Matcher reviews the SKU, and approves it based on its score. \n\n-`manual`, for manual approvals through the Received SKU UI, or Match API. \n\n-`autoApprove`, for every SKU received from a given seller to be approved automatically, regardless of their Matcher Score."
      operationId: Getaccountconfig
      parameters:
      - name: accountName
        in: path
        required: true
        description: Name of the VTEX account that belongs to the marketplace. All data extracted, and changes added will be posted into this account.
        schema:
          type: string
          default: apiexamples
      - name: Accept
        in: header
        description: HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      - name: Content-Type
        in: header
        description: Describes the type of the content being sent.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      responses:
        '200':
          description: OK
          headers: {}
          content:
            application/json:
              schema:
                type: object
                properties:
                  Score:
                    type: object
                    description: Matcher scores for approving and rejecting SKUs received from sellers.
                  Matchers:
                    type: array
                    description: All Matchers configured on the marketplace, and their respective details.
                  Rules:
                    type: object
                    description: Items and products.
                  SpecificationsMapping:
                    type: array
                    description: Mapping of product and SKU specifications, per seller.
                  MatchFlux:
                    type: string
                    description: This field determines the type of approval configuration applied to SKUs received from a seller.
              example:
                Score:
                  Approve: 80
                  Reject: 30
                Matchers:
                - MatcherId: vtex-matcher
                  hook-base-address: http://portal.vtexinternal.com/api/ssm/hooks
                  IsActive: true
                  UpdatesNotificationEndpoint: null
                  Description: null
                Rules:
                  Item: []
                  Product: []
                SpecificationsMapping: []
                MatchFlux: Default
      deprecated: false
    put:
      tags:
      - SKU Approval Settings
      summary: VTex Save Account's Approval Settings
      description: "Marketplaces use this endpoint to create or update approval settings on their Received SKUs module. \n\nThe request includes all the details necessary to implement the chosen approval settings."
      operationId: Saveaccountconfig
      parameters:
      - name: accountName
        in: path
        required: true
        description: Name of the VTEX account that belongs to the marketplace. All data extracted, and changes added will be posted into this account.
        schema:
          type: string
          default: apiexamples
      - name: Accept
        in: header
        description: HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      - name: Content-Type
        in: header
        description: Describes the type of the content being sent.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      requestBody:
        description: ''
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SaveaccountconfigRequest'
        required: true
      responses:
        '200':
          description: OK
          headers: {}
          content:
            application/json:
              schema:
                type: object
                example:
                  Score:
                    Approve: 80
                    Reject: 30
                  Matchers:
                  - MatcherId: vtex-matcher
                    hook-base-address: http://simple-suggestion-matcher.vtex.com.br
                    IsActive: true
                    UpdatesNotificationEndpoint: notification.endpoint
                    Description: Note
                  Rules:
                    Item:
                    - 1
                    Product:
                    - Shirt
                  SpecificationsMapping:
                  - SellerId: Store1
                    Mapping:
                      Yellow: Light yellow
                  MatchFlux: AutoApprove
                properties:
                  Score:
                    type: object
                    description: '[Matcher''s rates](https://help.vtex.com/en/tutorial/understanding-vtex-matcher-scoring) to approve or reject [received SKUs](https://help.vtex.com/en/tutorial/cataloging-received-skus--tutorials_396) sent by sellers.'
                    properties:
                      Approve:
                        type: integer
                        description: Score to approve SKUs sent by sellers.
                      Reject:
                        type: integer
                        description: Score to reject SKUs sent by sellers.
                    example:
                      Approve: 80
                      Reject: 30
                  Matchers:
                    type: array
                    description: '[Matchers](https://help.vtex.com/en/tutorial/understanding-vtex-matcher-scoring) configurations for approving and rejecting [received SKUs](https://help.vtex.com/en/tutorial/cataloging-received-skus--tutorials_396) sent by sellers.'
                    properties:
                      MatcherId:
                        type: string
                        description: Identifies the matching entity. It can be either [VTEX's matcher](https://help.vtex.com/en/tutorial/understanding-vtex-matcher-scoring), or an external matcher.
                      hook-base-address:
                        type: string
                        description: The given Matcher's URL.
                      IsActive:
                        type: boolean
                        description: Whether the matcher is active in the account (`true`), or not (`false`).
                      UpdatesNotificationEndpoint:
                        type: string
                        description: The [received SKUs](https://help.vtex.com/en/tutorial/cataloging-received-skus--tutorials_396) module calls this endpoint for matcher's suggestions updates.
                      Description:
                        type: string
                        description: The note inserted on the request body.
                  Rules:
                    type: object
                    description: Items and products that belong to sellers.
                    properties:
                      Item:
                        type: array
                        description: SKUs' ID.
                        items:
                          type: integer
                          description: SKU ID.
                      Product:
                        type: array
                        description: Product's name.
                        items:
                          type: string
                          description: Product name.
                  SpecificationsMapping:
                    type: array
                    description: This attribute maps product and SKU's specifications between the marketplace and the seller.
                    properties:
                      SellerId:
                        type: string
                        description: The Seller ID.
                      Mapping:
                        type: object
                        description: The attributes and values mapped between the marketplace and the seller.
                  MatchFlux:
                    type: string
                    description: "Type of approval configuration that apply to received SKUs sent by sellers. The possible values are: \n\n`default`: the matcher approves the SKU. \n\n`manual`: manual SKU's approvals. \n\n`AutoApprove`: automatic SKU's approvals."
      deprecated: false
  /suggestions/configuration/account/config:
    get:
      tags:
      - SKU Approval Settings
      summary: VTex Get Account's Matcher Settings
      description: "This endpoint will be used by the marketplace to query the matcher's current approval settings on their incoming SKUs module. If the account has no matcher configured, the response will be `404 Not Found`. \n\nFor account approval configuration information, with response including specification information, see [Get Account Approval Settings](https://developers.vtex.com/docs/api-reference/marketplace-apis- suggestions#get-/suggestions /configuration) terminal. \n\nThe [VTEX matcher](https://help.vtex.com/pt/tutorial/entendendo-a-punctuacao-do-vtex-matcher--tutorials_424) is a tool used by marketplaces to evaluate SKUs corresponding to information from an advertisement of the seller, with those of items already present in the marketplace catalog."
      operationId: Getmatchconfig
      parameters:
      - name: accountName
        in: path
        required: true
        description: Name of the VTEX account that belongs to the marketplace. All data extracted, and changes added will be posted into this account.
        schema:
          type: string
          default: apiexamples
      - name: Accept
        in: header
        description: HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      - name: Content-Type
        in: header
        description: Describes the type of the content being sent.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      responses:
        '200':
          description: OK
          headers: {}
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/responseGetAccountsMatcherSettings'
              example:
                score:
                  approve: 85
                  pending: 31
                  reject: 30
                matchers:
                - matcherId: example-matcher
                  hook-base-address: http://portal.vtexinternal.com.br/api/u90/hooks
                  isActive: true
                  updatesNotificationEndpoint: null
                  description: null
                rules:
                  item: []
                  product: []
                specificationsMapping: []
                matchFlux: Default
      deprecated: false
  /suggestions/configuration/seller/{sellerId}:
    get:
      tags:
      - SKU Approval Settings
      summary: VTex Get Seller's Approval Settings
      description: "This endpoint retrieves the current Received SKUs approval settings applied to a specific seller. Its response includes: \n\n- `sellerId`: A string that identifies the seller in the marketplace. \n\n- `accountId`: Marketplace’s account ID. \n\n- `accountName`: Marketplace’s account name. \n\n- `mapping`: Mapping of SKU and product Specifications. \n\n- `matchFlux`: This field determines the type of approval configuration applied to SKUs received  from a seller. \n\nThe possible values include:  \n\n-`default`, where the Matcher reviews the SKU, and approves it based on its score. \n\n-`manual`, for manual approvals through the Received SKU UI and Match API. \n\n-`autoApprove`, for every SKU received from a given seller to be approved automatically                                                   , regardless of the Matcher Score."
      operationId: Getselleraccountconfig
      parameters:
      - name: accountName
        in: path
        required: true
        description: Name of the VTEX account that belongs to the marketplace. All data extracted, and changes added will be posted into this account.
        schema:
          type: string
          default: apiexamples
      - name: sellerId
        in: path
        description: A string that identifies the seller in the marketplace. This ID must be created by the marketplace.
        required: true
        style: simple
        schema:
          type: string
          default: seller123
      - name: Accept
        in: header
        description: HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      - name: Content-Type
        in: header
        description: Describes the type of the content being sent.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/responseGetSellersApprovalSettings'
              example:
                sellerId: sellerexample
                accountId: d74dau71f-325a-4463-bd53-ae8b0453186ca
                accountName: marketplaceexample
                mapping:
                  defaultColor: white /black
                  searchColor: color1, color2
                  color1: black
                  color2: white
                  color: black
                  size: EUR44
                matchFlux: default
      deprecated: false
    put:
      tags:
      - SKU Approval Settings
      summary: VTex Save Seller's Approval Settings
      description: "Marketplaces use this endpoint to create or update approval settings to a specific seller, on the Received SKUs module. \n\nThe request includes all the details necessary to implement the chosen approval settings."
      operationId: Putselleraccountconfig
      parameters:
      - name: accountName
        in: path
        required: true
        description: Name of the VTEX account that belongs to the marketplace. All data extracted, and changes added will be posted into this account.
        schema:
          type: string
          default: apiexamples
      - name: sellerId
        in: path
        description: A string that identifies the seller in the marketplace. This ID must be created by the marketplace.
        required: true
        style: simple
        schema:
          type: string
          default: seller123
      - name: Accept
        in: header
        description: HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      - name: Content-Type
        in: header
        description: Describes the type of the content being sent.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      requestBody:
        description: ''
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PutselleraccountconfigRequest'
            example:
              sellerId: 1a
              mapping: null
              matchFlux: Default
        required: true
      responses:
        '200':
          description: OK
          headers: {}
      deprecated: false
  /suggestions/configuration/autoapproval/toggle/seller/{sellerId}:
    put:
      tags:
      - SKU Approval Settings
      summary: VTex Activate autoApprove Setting for a Seller
      description: This endpoint enables the auto approve setting to received SKUs from a specific seller. Be aware that once enabling the rule through this request, all received SKUs from that seller will be automatically approved on your store, regardless of the Matcher Score.
      operationId: Saveautoapproveforaccountseller
      parameters:
      - name: accountName
        in: path
        required: true
        description: Name of the VTEX account that belongs to the marketplace. All data extracted, and changes added will be posted into this account.
        schema:
          type: string
          default: apiexamples
      - name: sellerId
        in: path
        description: A string that identifies the seller in the marketplace. This ID must be created by the marketplace.
        required: true
        style: simple
        schema:
          type: string
          default: seller123
      - name: Accept
        in: header
        description: HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      - name: Content-Type
        in: header
        description: Describes the type of the content being sent.
        required: true
        style: simple
        schema:
          type: string
          default: application/json
      requestBody:
        description: ''
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SaveautoapproveforaccountsellerRequest'
            example:
              Enabled: true
        required: true
      responses:
        '200':
          description: OK
          headers: {}
      deprecated: false
components:
  schemas:
    responseGetSellersApprovalSettings:
      title: GetSellersApprovalSettings
      type: object
      properties:
        sellerId:
          type: string
          description: A string that identifies the seller in the marketplace.
          example: sellerexample
        accountId:
          type: string
          description: Marketplace’s account ID.
          example: d74daf1f-355a-4463-bdc7-ae8b045311c
        accountName:
          type: string
          description: Marketplace’s account name.
          example: marketplaceexample
        mapping:
          type: object
          default: {}
          description: "SKU Mapping Information and Product [Specifications](https://developers.vtex.com/docs/guides/catalog-overview#configuring-initial-settings-mandatory).\n\n The properties included within `mapping` can change according to the product type, the `color` specification and its variations described in this example are just one of the possibilities. The values received in this call's payload for those properties depend on the seller's catalog architecture, and are not default. \n\nSee some examples of specifications: \n\n- Voltage \n\n- Power \n\n- Size \n\n- Height \n\n- Width"
          properties:
            defaultColor:
              type: string
              description: 'The field will indicate the default color predefined by the seller in cases where specific product colors are not defined. This field is neither mandatory nor default, it will depend on the architecture of the seller''s catalog. '
              example: white /black
            searchColor:
              type: string
              description: Field that provides the available colors to filter searches. This field is neither mandatory nor default, it will depend on the architecture of the seller's catalog.
              example: color1, color2
            color1:
              type: string
              description: '`color1` available for search filter. This field is neither mandatory nor default, it will depend on the architecture of the seller''s catalog.'
              example: black
            color2:
              type: string
              description: '`color2` available for search filter. This field is neither mandatory nor default, it will depend on the architecture of the seller''s catalog.'
              example: white
            color:
              type: string
              description: Indicates the predominant or main color of the product. This field is neither mandatory nor default, it will depend on the architecture of the seller's catalog.
              example: black
            size:
              type: string
              description: Indicates the size of the product.This field is neither mandatory nor default, it will depend on the architecture of the seller's catalog.
              example: EUR44
        matchFlux:
          type: string
          description: "This field determines the type of [approval configuration applied to SKUs received from a seller](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/configuration/seller/-sellerId-). \n\nThe possible values include:  \n\n-`default`, where the Matcher reviews the SKU, and approves it based on its score. \n\n-`manual`, for manual approvals through the Received SKU UI and Match API. \n\n-`autoApprove`, for every SKU received from a given seller to be approved automatically, regardless of the Matcher Score."
          example: default
    PutselleraccountconfigRequest:
      title: PutselleraccountconfigRequest
      required:
      - sellerId
      - mapping
      - matchFlux
      type: object
      properties:
        sellerId:
          type: string
          description: A string that identifies the seller in the marketplace. This ID must be created by the marketplace.
          default: seller123
        mapping:
          type:
          - object
          - 'null'
          description: 'Mapping of SKU and product Specifications. This object should be sent in the following format for all fields you wish to map:


            {specificationName}:{specificationValue},


            Example:


            Choose voltage: Voltage,


            Choose size: Size'
          default:
            Choose voltage: Voltage
            Choose size: Size
            Choose volume: Volume
            Choose type: Type
        matchFlux:
          type: string
          description: "This field determines the type of approval configuration applied to SKUs received  from a seller. The possible values include: \n\n- `default` where the Matcher reviews the SKU, and approves it based on its score \n\n- `manual` for manual approvals through the Received SKU UI or Match API \n\n- `autoApprove` for every SKU received from a given seller to be approved automatically, regardless of the Matcher Score."
          default: autoApprove
    responseGetAccountsMatcherSettings:
      title: GetAccountsMatcherSettings
      description

# --- truncated at 32 KB (39 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/vtex/refs/heads/main/openapi/vtex-sku-approval-settings-api-openapi.yml