events/get-calendar-settings returns the calendar’s stored settings as rows: key, value, and whether the value was withheld.
Credentials are redacted rather than omitted, so a caller can tell that a map API key is configured without being handed it.
At a glance
| Ability | events/get-calendar-settings |
| Toolset | The Events Calendar — toolset/events-calendar |
| Group | The Events Calendar › Calendar Settings |
| Requires | The Events Calendar, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
The Events Calendar keeps its settings in a single option shared by the calendar, the ticketing plugin and every add-on on the site. Date formats and week-start sit in the same array as Google Maps API keys and social platform access tokens. There is no clean separation to read along.
So the redaction is by key: anything matching the credential patterns comes back with a null value and a redacted flag set. The key itself is still visible, which is usually the actual question — is the maps key configured? is answerable without the key ever leaving the site.
Licence keys are not here at all. They live in separate options, and this ability does not read them. That is a stronger guarantee than redaction: a value that is never fetched cannot leak through a logging path or an error message.
The response reports how many keys were redacted, so the count is visible even when the values are not.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
settings | array | One row per setting: key, value, and a redacted flag. Redacted rows carry a null value. |
count | integer | How many settings were returned. |
redacted | integer | How many of them had their value withheld. |
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:
How is the calendar configured, and is the maps API key set?
It resolves to one call:
{
"ability": "events/get-calendar-settings",
"parameters": {}
}Worth knowing
- Read-only. There is no companion ability that writes these — the blob is shared across plugins, and a partial write to it is a good way to break several at once.
- A redacted row means the setting exists and has a value. An absent key means it was never set.
- Licence keys are in separate options and are never read here.
- Add-ons write into the same option, so the keys you see depend on what is installed.
Related abilities
- List Events — the data these settings shape
- List Event Categories — the taxonomy side of the setup
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category