canonical: https://jentic.com/apis/vtex.local/marketplace-api

# Vtex Marketplace API

The **Marketplace API** enables marketplaces and sellers hosted on VTEX to perform their collaborative operations. >⚠️ 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. Index Notification Endpoints used by sellers to notify marketplaces that the price or inventory language ha. The API exposes 22 endpoints secured with apiKey authentication.

## For AI agents

Programmatically notify marketplace of price update, notify marketplace of inventory update. Covers 22 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Notify marketplace of price update
- Get matched offers list
- Invite seller lead
- List seller leads
- Monitor Marketplace API operational status and events

## Use cases

### E-Commerce Operations

Use the Marketplace API to perform e commerce operations programmatically. The API provides 22 endpoints covering core functionality including notify marketplace of price update, notify marketplace of inventory update, get matched offers list.

Example prompt: Call POST `/notificator/{sellerId}/changenotification/{skuId}/price` to notify marketplace of price update

### Automated Sellers Management

Automate sellers operations by combining multiple Marketplace API endpoints. Agents can notify marketplace of inventory update and then get matched offers list in a single workflow.

Example prompt: Call POST `/notificator/{sellerId}/changenotification/{skuId}/inventory` to notify marketplace of inventory update, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Marketplace API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'notify marketplace of price update', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/notificator/{sellerId}/changenotification/{skuId}/price` | Notify marketplace of price update |
| POST | `/notificator/{sellerId}/changenotification/{skuId}/inventory` | Notify marketplace of inventory update |
| GET | `/offer-manager/pvt/offers` | Get matched offers list |
| GET | `/offer-manager/pvt/product/{productId}/sku/{skuId}` | Get matched offers' data by SKU ID |
| GET | `/offer-manager/pvt/product/{productId}` | Get matched offers' data by product ID |
| POST | `/seller-register/pvt/seller-leads` | Invite seller lead |
| GET | `/seller-register/pvt/seller-leads` | List seller leads |
| GET | `/seller-register/pvt/seller-leads/{sellerLeadId}` | Get seller lead's data by ID |

## Key resources

- **Sellers** — Operations related to Sellers
- **Seller Invite** — Operations related to Seller Invite
- **Seller Commissions** — Operations related to Seller Commissions
- **Notification** — Operations related to Notification
- **Matched Offers** — Operations related to Matched Offers

## Why Jentic

- **Setup:** Wiring the VTEX Marketplace API by hand means pairing an App Key with an App Token in the X-VTEX-API-AppKey and X-VTEX-API-AppToken headers, and templating the {accountName} and {environment} host into every call. Through Jentic you install once, import the Marketplace API from the API Directory, store the App Key and App Token once, and your agent calls it.
- **Permission scoping:** The Marketplace API puts the seller id and product id in the URL path (`/notificator/{sellerId}/changenotification/{skuId}/price` and `/offer-manager/pvt/product/{productId}`), so a rule can pin your agent to one seller or product. You choose the operations it may call, so writes like sending price or inventory change notifications are not included unless you add them.
- **Credential handling:** Your VTEX App Key and App Token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'notify the marketplace of a price update' or 'list seller offers', and Jentic returns the matching Marketplace API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Marketplace API use?

The Marketplace API uses an API key passed in the `X-VTEX-API-AppKey` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I notify marketplace of price update with the Marketplace API?

Yes. Use the POST `/notificator/{sellerId}/changenotification/{skuId}/price` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Marketplace API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I notify marketplace of price update through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'notify marketplace of price update'. Jentic returns the matching Marketplace API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Marketplace API have?

The Marketplace API exposes 22 endpoints covering sellers, seller invite, seller commissions operations.

### Can I limit what my agent is allowed to do with the Marketplace API?

Yes. Because you run Jentic One yourself, your own rules decide which Marketplace API operations and credentials the agent may use, so you can allow read calls like GET `/offer-manager/pvt/offers` or listing seller leads while excluding writes such as POST `/notificator/{sellerId}/changenotification/{skuId}/price.` Since the seller id and product id sit in the URL path, a rule can pin the agent to a single seller or product. Nothing is exposed to the agent unless you add that operation to its allowed set.