Vtex Marketplace API
Browse all Vtex APIs65
AI ReadinessAI-Aware (B)65/100
E CommerceInventoryapiKey22 EndpointsREST
For Agents
Programmatically notify marketplace of price update, notify marketplace of inventory update. Covers 22 operations with apiKey authentication.
Use for: I need to notify marketplace of price update, I want to notify marketplace of inventory update, Search for matched offers list, Find all matched offers' data by sku id
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
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.
Install Jentic One Beta
Connect the Marketplace API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Marketplace API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fvtex.local%2Fmarketplace-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fvtex.local%2Fmarketplace-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Marketplace API.
Notify marketplace of price update
Get matched offers list
Invite seller lead
List seller leads
Monitor Marketplace API operational status and events
Use Cases
Patterns agents use Marketplace API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'notify marketplace of price update', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
22 endpoints — the **marketplace api** enables marketplaces and sellers hosted on vtex to perform their collaborative operations.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
M
Marketplace API
- AI-Aware (B)65/100
57
Foundational Compliance63
Developer Experience & Jentic Compatibility61
AI-Readiness & Agent Experience94
Agent Usability50
Security74
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
57
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C+Signals: 4
70%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
60%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
35%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
93%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
61
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: B-Signals: 4
82%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
61%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
74
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
74%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
FAQs
Specific to using Marketplace API through Jentic.
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.
GET STARTED