VTEX DO API

Name: VTEX DO API
Brand: VTEX DO API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontapiKey8 EndpointsREST

Install Jentic One Beta

Connect the VTEX DO API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the VTEX DO 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.

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%2Fvtex-do-api" | sh

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%2Fvtex-do-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 VTEX DO API.

Create note

Get notes by order ID

Retrieve note

List tasks

GET STARTED

Start building with VTEX DO API

Explore with Jentic One

View OpenAPI Document

[VTEX DO](https://help.vtex.com/en/tutorial/vtex-do--7KMbRL4OslN8DTX9oiuCiu) is a task management system for authorized [users](https://help.vtex.com/en/tutorial/how-to-manage-users--tutorials_512) to process VTEX store orders. The functionality allows you to control notes, and create, update, list, and retrieve tasks. VTEX DO API Index Note - `POST` [Create Note](https://developers.vtex.com/docs/. The API exposes 8 endpoints secured with apiKey authentication.

Use Cases

Patterns agents use VTEX DO API for, with concrete tasks.

★ E-Commerce Operations

Use the VTEX DO API to perform e commerce operations programmatically. The API provides 8 endpoints covering core functionality including create note, get notes by order id, retrieve note.

Call POST /notes to create note

Automated Note Management

Automate note operations by combining multiple VTEX DO API endpoints. Agents can get notes by order id and then retrieve note in a single workflow.

Call GET /notes to get notes by order id, then verify the result

AI Agent Integration via Jentic

AI agents discover and call VTEX DO 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 'create note', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

8 endpoints — [vtex do](https://help.

METHOD

PATH

DESCRIPTION

POST

/notes

Create note

GET

/notes

Get notes by order ID

GET

/notes/{noteId}

Retrieve note

POST

/tasks

Create task

GET

/tasks

List tasks

GET

/tasks/{taskId}

Retrieve task

PUT

/tasks/{taskId}

Update task

POST

/tasks/{taskId}/comments

Add comment on a task

POST

/notes

Create note

GET

/notes

Get notes by order ID

GET

/notes/{noteId}

Retrieve note

POST

/tasks

Create task

GET

/tasks

List tasks

GET

/tasks/{taskId}

Retrieve task

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the VTEX DO API by hand means setting the X-VTEX-API-AppKey and X-VTEX-API-AppToken header pair, building the accountName and environment host from your VTEX region, and managing that yourself. Through Jentic you install once, import the VTEX DO API from the API Directory, store the app key and token once, and your agent calls it.

Permission scoping

The VTEX DO API puts the resource id in the URL path (/tasks/{taskId} and /notes/{noteId}), so a rule can pin your agent to one task or note. You choose the operations it may call, so you can allow reading and commenting on tasks while a write like updating a task is not included unless you add it.

Credential isolation

Your VTEX DO app key and 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 'create a task' or 'list open notes', and Jentic returns the matching VTEX DO 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

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using VTEX DO API through Jentic.

What authentication does the VTEX DO API use?

The VTEX DO 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 create note with the VTEX DO API?

Yes. Use the POST /notes endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the VTEX DO 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 create note through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create note'. Jentic returns the matching VTEX DO API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the VTEX DO API have?

The VTEX DO API exposes 8 endpoints covering note, task operations.

Can I limit what my agent is allowed to do with the VTEX DO API?

Yes. Because you run Jentic One yourself, your own rules decide which VTEX DO operations and credentials the agent may use. Since the resource id sits in the URL path, such as /tasks/{taskId} and /notes/{noteId}, you can pin the agent to a single task or note, and you choose the operations it may call. For example, you can allow reading tasks and adding comments while leaving updating a task out unless you add it.