WordPress
Coming soonAPI key
Open-source content management system
WordPress is in the catalog but is not connectable yet. It appears in Integrations with a Coming soon label and no Connect action, so there is nothing to set up today. The rest of this page describes what the connection is intended to do.
What moves, and which way
Integrations run in both directions. What follows is what this connection is for.
En Garde to WordPress
- Files, exports, and event payloads En Garde produces.
WordPress to En Garde
- Objects, repository or deployment events, and identity records the service exposes.
How it will connect
You generate a key in the platform and paste it into En Garde. The key is tested against the live API before it is stored, so a wrong or under-scoped key fails at setup rather than silently later.
These steps describe the standard API key flow. They do not work for WordPress yet, because the connection has not shipped.
- Generate an API key in the platform, with the permissions its documentation lists for third-party access.
- Open Integrations in your Brand Space and find the platform on the Integrations tab.
- Click Connect. Paste the key into the API key field — the eye toggle reveals what you pasted so you can check it.
- Click Test Connection. En Garde calls the platform with the key and reports whether it worked.
- Save. The Save button will not store an untested key, so a failing test has to be fixed first.