mailerpress/manage-api-keys handles MailerPress API-key lifecycle through one surface: list, create, update, revoke, reactivate and delete.
These are integration API keys for MailerPress’s own admin API — distinct from the Pro embed keys, which are a different thing for a different purpose.
Before you run it
The raw key is returned once, on creation, and MailerPress cannot re-issue it — a response not captured means the key is unusable. The delete operation is a hard delete requiring confirm_id; revoke is the soft version that marks a key inactive and can be reversed with reactivate.
At a glance
| Ability | mailerpress/manage-api-keys |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Settings & Delivery |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Destructive in its delete operation — requires confirm_id. The raw key is returned once on creation and never again. |
| Repeatable | Not idempotent — each call changes the row set, so re-running is not a no-op |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
Creation returns metadata plus the raw key, and that is the only moment the key exists in readable form. It is stored one-way afterwards, so a response that is not captured leaves a key nobody can use and which still appears in the listing.
Revoke and delete are deliberately different. Revoking marks a key inactive, which stops it working and keeps the record — reversible with reactivate, and the right response to a key you suspect rather than know about.
Deleting is hard and permanent, and requires confirm_id matching the key’s ID.
Revoking first is the safer sequence: stop the key, see what breaks, and delete once you know what used it.
These keys grant access to MailerPress’s admin API, which reaches contacts and campaigns. A leaked key is a contact-data exposure rather than an inconvenience.
Not idempotent for create and delete.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
action | string | Yes | list, create, update, revoke, reactivate or delete. |
id | integer | For all but list and create | The key. |
confirm_id | integer | For delete | Must match id. |
name | string | For create and update | What the key is for. |
confirm | boolean | Yes — must be true | The irreversibility gate. Without it the call is refused before anything is touched. |
What comes back
| Name | Type | What it is |
|---|---|---|
key | string | The raw key — on creation only, and never again. |
keys | array | The key metadata, for list. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Create an API key for the integration.
It resolves to one call:
{
"ability": "mailerpress/manage-api-keys",
"parameters": {
"action": "create",
"name": "CRM integration"
}
}Worth knowing
- The raw key is returned once. Capture it or start again.
- Revoke is reversible; delete is not.
- Revoke first, observe what breaks, then delete.
- These keys reach contact data. A leak is an exposure.
Related abilities
- MailerPress Pro List Embed Keys — the different Pro key type
- MailerPress Manage Settings — the rest of the configuration
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category