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

# Vtex Pricing API

Check the new [Pricing onboarding guide](https://developers.vtex.com/docs/guides/pricing-overview). We created this guide to improve the onboarding experience for developers at VTEX. It assembles all documentation on our Developer Portal about Pricing and is organized by focusing on the developer's journey. Pricing is the VTEX module responsible for the SKU's price list. In this module, we have th. The API exposes 16 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get price by sku id, create or update base price or fixed price. Covers 16 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- Get price by SKU ID
- Create or update base price or fixed price
- Delete price all base and fixed prices of an SKU
- Query and filter Pricing API records by parameters
- Monitor Pricing API operational status and events

## Use cases

### HR and Recruiting Operations

Use the Pricing API to perform hr recruiting operations programmatically. The API provides 16 endpoints covering core functionality including get price by sku id, create or update base price or fixed price, create or update base price or fixed price.

Example prompt: Call GET `/pricing/prices/{itemId}` to get price by sku id

### Automated Price Tables Management

Automate price tables operations by combining multiple Pricing API endpoints. Agents can create or update base price or fixed price and then create or update base price or fixed price in a single workflow.

Example prompt: Call PUT `/pricing/prices/{itemId}` to create or update base price or fixed price, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Pricing 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 'get price by sku id', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/pricing/prices/{itemId}` | Get price by SKU ID |
| PUT | `/pricing/prices/{itemId}` | Create or update base price or fixed price |
| PATCH | `/pricing/prices/{itemId}` | Create or update base price or fixed price |
| DELETE | `/pricing/prices/{itemId}` | Delete price all base and fixed prices of an SKU |
| GET | `/pricing/prices/{itemId}/fixed` | Get fixed prices |
| POST | `/pricing/prices/{itemId}/fixed/{priceTableId}` | Create or update fixed prices on a price table or trade policy |
| GET | `/pricing/prices/{itemId}/fixed/{priceTableId}` | Get fixed prices on a price table or trade policy |
| DELETE | `/pricing/prices/{itemId}/fixed/{priceTableId}` | Delete fixed prices on a price table or trade policy |

## Key resources

- **Price Tables** — Operations related to Price Tables
- **Prices and Fixed Prices** — Operations related to Prices and Fixed Prices
- **Pricing Configuration** — Operations related to Pricing Configuration

## Why Jentic

- **Setup:** Wiring the VTEX Pricing 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 api.vtex.com/{accountName} host into every call. Through Jentic you install once, import the Pricing API from the API Directory, store the App Key and App Token once, and your agent calls it.
- **Permission scoping:** The Pricing API puts the item id in the URL path (`/pricing/prices/{itemId}`), so a rule can pin your agent to one item and its fixed prices. You choose the operations it may call, so destructive ones like deleting a price or a fixed price entry 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 'get the price for an item' or 'set a fixed price for an item', and Jentic returns the matching Pricing API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the Pricing API use?

The Pricing 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 get price by sku id with the Pricing API?

Yes. Use the GET `/pricing/prices/{itemId}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Pricing 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 get price by sku id through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get price by sku id'. Jentic returns the matching Pricing API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The Pricing API exposes 16 endpoints covering price tables, prices and fixed prices, pricing configuration operations.

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

Yes. Jentic One runs self-hosted, so your own rules decide which Pricing API operations and credentials the agent may use. Because the item id sits in the URL path (`/pricing/prices/{itemId}`), you can pin the agent to a single item and its fixed prices, and you pick the exact operations it may call, such as GET `/pricing/prices/{itemId}` to read a price while excluding destructive ones like DELETE `/pricing/prices/{itemId}.` Your VTEX App Key and App Token stay stored encrypted in your instance and are injected only for the operations you approve.