Message Center API

Name: Message Center API API
Brand: Message Center API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayouts TransfersapiKey1 EndpointsREST

For Agents

Programmatically generate dkim keys. Covers 1 operations with apiKey authentication.

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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Message Center API API.

Generate DKIM keys

Manage payments data programmatically

Integrate Message Center API into automated workflows

Query and filter Message Center API records by parameters

GET STARTED

Start building with Message Center API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Message Center API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Message Center API 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 though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Message Center API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'generate dkim keys') and Jentic returns the matching Message Center API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Message Center API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

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

Alternative

Adyen

Alternative payments API

Choose Adyen when you need a different approach to payments operations

Complementary

Square

Complementary payments API

Choose Square when you need a complementary approach to payments operations

Complementary

Paypal

Complementary payments API

Choose Paypal when you need a complementary approach to payments operations

FAQs

Specific to using Message Center API 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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.