WPCentrify REST API and webhooks (planned)

Where the API stands today

There is no public API, no API tokens and no webhooks in WPCentrify yet. They are planned, and listed on the roadmap. Until then, you run every site from the dashboard, alerts arrive by email, and automation rules handle the routine work without any code.

The plan below shows what the API is meant to cover. Names, scope and limits may change before it ships, so please do not build against it yet.

What the WordPress management API is planned to cover

• Connected sites, with their health, versions and tags
• Pending updates across the portfolio, with their risk scores
• Applying an update from your own systems
• Backups, and starting a full or selective restore
• Uptime incidents, with how long they lasted
• Vulnerabilities matched to the versions each site runs
• The activity log, so every action can be pulled into your own tools
• Client reports and the data behind them

Planned webhooks

Webhooks are planned to send an event to an address you choose when something happens on a site: an update applied, failed or rolled back, a backup completed or failed, a site going down or recovering, a vulnerability found or patched, a report sent, or a certificate or domain close to expiry. Each delivery is planned to be signed, so your system can check it really came from WPCentrify.

What you can use instead today

• Automation rules run updates, holds and rollbacks on a schedule or when something happens, with no code.
• Email alerts tell you when a site goes down, an update fails or a vulnerability needs action.
• The activity log records every action on every site, with who did it and when.