Create ses
Receives Amazon SES events as an SNS HTTPS subscription delivers them.
POST /v1/email/webhooks/ses
| Address | https://api.hanzo.ai/v1/email/webhooks/ses |
| Method | POST |
| Operation | post_email_webhooks_ses |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Receives Amazon SES events as an SNS HTTPS subscription delivers them. The organization is named in the address (?org=) and holds the SNS topic its events arrive on (the sns-topic-arn credential): a message is accepted when it is signed by SNS, is from that topic, and its certificate comes from that topic's region. A subscription confirmation is completed the same way and records nothing.
POST /v1/email/webhooks/ses?org=<org>
Request
The document declares no body for POST /v1/email/webhooks/ses. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask MCP's describe for post_email_webhooks_ses, which answers from the running route.
Response
The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.
Examples
hanzo email webhooks sesimport { Configuration, EmailApi } from 'hanzoai';
const api = new EmailApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postEmailWebhooksSes();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import EmailApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = EmailApi(client).post_email_webhooks_ses()cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.EmailAPI.PostEmailWebhooksSes(context.Background()).Execute()
if err != nil {
return err
}use hanzo_client::apis::{configuration::Configuration, email_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = email_api::post_email_webhooks_ses(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.EmailApi;
ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));
var result = new EmailApi(client).postEmailWebhooksSes();curl -X POST https://api.hanzo.ai/v1/email/webhooks/ses \
-H "Authorization: Bearer $HANZO_API_KEY"MCP reaches email through the email tool, which names its 8 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_emails"
}
}
}'