Vtex Message Center API
Browse all Vtex APIsPaymentsPayouts TransfersapiKey1 EndpointsREST
For Agents
Programmatically generate dkim keys. Covers 1 operations with apiKey authentication.
Use for: I need to generate dkim keys, Find available payments operations, Get the current status of Message Center API resources, List all records from Message Center API
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
Message Center corresponds to [order transactional email templates](https://help.vtex.com/en/tutorial/order-transactional-email-templates--3g2S2kqBOoSGcCaqMYK2my). The store can configure templates to automatically send emails to customers and notify them about their order events, such as payment confirmation and shipping. Message Center API Index DKIM configuration - `POST` [Generate DKIM keys](h. The API exposes 1 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Message Center API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Message Center 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%2Fmessage-center-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%2Fmessage-center-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 Message Center API.
Generate DKIM keys
Manage payments data programmatically
Integrate Message Center API into automated workflows
Query and filter Message Center API records by parameters
Monitor Message Center API operational status and events
Use Cases
Patterns agents use Message Center API for, with concrete tasks.
★ Payments Operations
Use the Message Center API to perform payments operations programmatically. The API provides 1 endpoints covering core functionality including generate dkim keys.
Call POST /api/mail-service/pvt/providers/{EmailProvider}/dkim to generate dkim keys
Data Retrieval and Monitoring
Query Message Center API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Message Center API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Message Center 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 'generate dkim keys', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
1 endpoints — message center corresponds to [order transactional email templates](https://help.
METHOD
PATH
DESCRIPTION
POST
/api/mail-service/pvt/providers/{EmailProvider}/dkim
Generate DKIM keys
POST
/api/mail-service/pvt/providers/{EmailProvider}/dkim
Generate DKIM keys
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the VTEX Message Center 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 the call. Through Jentic you install once, import the Message Center API from the API Directory, store the App Key and App Token once, and your agent calls it.
Permission scoping
The Message Center API puts the email provider in the URL path (/api/mail-service/pvt/providers/{EmailProvider}/dkim), so a rule can pin your agent to one email provider. This surface exposes a single operation, generating DKIM keys, so you grant only that operation and nothing else.
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 'generate DKIM keys for an email provider', and Jentic returns the matching Message Center 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 payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using Message Center API through Jentic.
What authentication does the Message Center API use?
The Message Center 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 generate dkim keys with the Message Center API?
Yes. Use the POST /api/mail-service/pvt/providers/{EmailProvider}/dkim endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Message Center 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 generate dkim keys through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'generate dkim keys'. Jentic returns the matching Message Center API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Message Center API have?
The Message Center API exposes 1 endpoints covering dkim configuration operations.
Can I limit what my agent is allowed to do with the Message Center API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The Message Center API exposes a single operation, generating DKIM keys via POST /api/mail-service/pvt/providers/{EmailProvider}/dkim, so you can grant that one call and nothing else. Since the email provider sits in the URL path, you can also pin the agent to one specific provider.
GET STARTED