Every action in Wordify Console is a REST endpoint. Provision sites, push to staging, take backups and bump PHP from your own code, with one bearer token.
Create a token in Integrations → API Tokens and grant it only the abilities it needs. A read-only reporting token and a provisioning token are different tokens.
Standard REST over HTTPS, JSON in and JSON out. GET /me orients you, and every response tells you what you can do next.
Long-running work returns a task handle you poll. Every call runs as you, under your team role, and lands in your Activity Log.
Grouped by the job, not the endpoint. If you can do it in the dashboard, you can script it.
Create WordPress sites, clone them, check plans and regions.
POST /sites stands up real hosting.
Create a staging site, push it live, pull live back down.
Wire it into your deploy pipeline.
Create on demand, list what you hold, restore when it matters, download the archive.
Back up before every release.
PHP version, cache, CDN, Redis, wp-config, debug mode and basic auth, all addressable.
Bump PHP fleet-wide from a script.
List, install, enable, disable.
Roll a plugin change across a fleet from CI.
Read the WordPress debug log, flip WP_DEBUG, follow long-running tasks to completion.
Pull debug.log into your own alerting.
One action across many sites, asynchronously, with a pollable handle back.
POST /tasks dispatches the fleet.
Attach custom domains, re-check DNS once you have pointed it.
Finish onboarding without a dashboard.
Team context, access, usage and invoices, so your own billing views stay in sync.
Reconcile usage in your own system.
Most hosting APIs are generated CRUD over database rows. Ours was designed to be operated by code and by agents, so the responses carry their own context.
display_name on every resource. The API tells you what a thing is called, not just its ID. available_actions on every response. Your client does not have to hardcode the state machine. { error: { code, message, details?, request_id } } One error envelope. Match on code, never on a message string. 202 Accepted Async built in from the start. Long-running and fleet-wide actions return a task handle. Nothing is bolted on. The REST API is the foundation. Our AI connector is built on it, and adds purpose-built tools for agents on top, like auditing a whole fleet and dispatching the fixes in a single call. Script it from your own code, or talk to it in plain English.
Meet the AI connector❯ POST /sites from your onboarding form
⏺ Site live in Sydney, domain attached, DNS verified
A new client signs up in your own system. Your code provisions the site in the right region, attaches the domain and checks DNS, before anyone opens a dashboard.
❯ POST /sites/{id}/staging/push in CI
⏺ Staging pushed to live, backup taken first
Back up, push staging to live, run your smoke tests. The release process you already have, with hosting as one more step in it.
❯ POST /tasks across 29 sites
⏺ 24 sites upgraded to PHP 8.4
One call dispatches an action across every site that needs it, and returns a handle you poll until it is done.
❯ GET /sites?filter[...] on a schedule
⏺ Nightly fleet report in your own dashboard
Pull site state on a cron and render it wherever your team already looks, instead of asking them to log into one more panel.
Abilities limit each token to exactly what you grant it: sites:read, sites:manage, teams:manage and the rest. A reporting token cannot provision.
Calls run under your account and your team role. An API token never widens your access.
API actions are attributed to your user and appear in the Activity Log like any other action.
Kill a token from Integrations → API Tokens the moment you need to.
Backups, staging and task creation sit in a tighter bucket than ordinary reads.
Yes. The REST API is included on every Wordify plan, with no add-on and no plan restriction. If you have a Wordify account, you already have it.
With a bearer token you mint in Console under Integrations → API Tokens. Tokens start wpk_ and carry scoped abilities, so each one can do only what you granted it.
https://console.wordify.com/api/v1. Call GET /me first to confirm your token and see your team context.
They run on the same foundation: the same permissions, the same audit log, the same bulk task engine. The REST API is the granular control plane you build on. The AI connector sits on top of it and adds tools built specifically for agents, like auditing a whole fleet and dispatching the fixes in one call. Use the API from your own code, and the connector from Claude or ChatGPT.
Yes. POST /sites provisions real WordPress hosting, including the install, DNS and SSL. It returns a task handle you poll while the site comes up, then you attach a custom domain.
Anything slow returns 202 Accepted with a task handle. Poll GET /tasks/{id} until it reaches a terminal state. The same engine powers fleet-wide bulk actions.
60 requests a minute for reads and standard mutations, 10 a minute for sensitive actions like backups and staging, and 300 a minute for MCP-tier tokens. Every response carries X-RateLimit-* headers.
v1 is stable for at least 12 months from public launch, and any breaking change carries a six-month Sunset notice. Additive changes are not breaking.
We publish the OpenAPI document in Console, at console.wordify.com/docs/api.json, so you can generate a typed client in your language of choice.
Yes, and people do. Provisioning, domains and login links are the building blocks of a white-label WordPress backend. If you are embedding Wordify in your own product, talk to us.
Prefer to talk to your hosting instead? Meet the AI connector.
Already a customer? Your token is two clicks away in Console. New to Wordify? Start hosting with us, and script it from day one.