PostShiba

[!NOTE] PostShiba skills connect agents to MCP for first send, domains, inboxes, and sandbox mail.

WordPress plugin that sends wp_mail through PostShiba.

Not on WordPress.org yet.

Installation

Clone postshiba/postshiba-wordpress into wp-content/plugins/postshiba and activate the plugin.

git clone https://github.com/postshiba/postshiba-wordpress wp-content/plugins/postshiba

Open pull requests on postshiba/sdks.

How It Works

The plugin hooks pre_wp_mail. After you set an API key and from address under Settings → PostShiba, WordPress mail posts to /api/v1/emails. WooCommerce and other plugins that call wp_mail go through the same hook. There is no WooCommerce module.

These constants override the saved options when they are defined: POSTSHIBA_API_KEY, POSTSHIBA_FROM_EMAIL, POSTSHIBA_FROM_NAME, POSTSHIBA_BASE_URL, POSTSHIBA_CLUSTER_ID, POSTSHIBA_ENABLED.

Send an email

wp_mail(
  "you@example.com",
  "PostShiba test",
  "hello from PostShiba"
);

Set a cluster id under Settings → PostShiba, or define POSTSHIBA_CLUSTER_ID. The plugin then sends X-Capsule-Cluster-Id on POST /api/v1/emails. Omit it and the header is not sent.

define('POSTSHIBA_CLUSTER_ID', 'NmQpXr');

Settings

Open Settings → PostShiba. Set the API key, from email, optional from name, optional base URL, and optional cluster id. The default base URL is https://app.postshiba.com. Use Send test email to mail the current user.

Errors and throttling

A failed send returns false from wp_mail. The API body fields are error, field, and message.

If error is throttled, the cluster hit its hourly send limit. Do not retry that send immediately. Immediate retries hit the same cap. Wait until the next hour.

Contributing

composer test

Tests mock HTTP. They do not call production.