Create a real WordPress site from your code and get back a URL that's already logged in. One token, one endpoint, every plan including the $2 sandbox.
Authenticate with a bearer token, POST to one endpoint, and get JSON back with a live URL and an autologin. Copy the call in curl, JavaScript, or PHP.
Everything the instawp CLI does, the API does. The CLI is this API with a terminal on top.
Base URL https://app.instawp.io/api/v2 · Header Authorization: Bearer <token>
Full endpoint and param list lives in the API reference.
Token auth and scopes, full create, configure and delete, lifecycle webhooks, branded client dashboards you build on the API, and throwaway sites in CI. The same surface the CLI drives.
Create named tokens in My Account → API Token, and scope each one read-only or read-write. Drop a token into GitHub Actions, a CI runner or a service, and every request carries a Bearer header. Revoke one without touching the rest.
Create from a template or from scratch, list with filters like ?type=reserved, retrieve a site's details, and delete when you're done. Mark a site reserved to keep it, or temporary to let it expire. One JSON shape in, one out.
Register a destination URL and pick an event, site.create or site.delete. InstaWP POSTs JSON to you, with an optional secret so you can verify it's really us. Every attempt shows up in Event Deliveries with the HTTP code, response time and timestamp.
| Event | Code | Response | Attempts | When |
|---|---|---|---|---|
| site.create | 200 | 142ms | 1 | 12:04:11 |
| site.delete | 200 | 118ms | 1 | 11:58:02 |
| site.create | 200 | 96ms | 1 | 11:51:47 |
Call the same REST API from your own app to list, spin up, and manage every client's WordPress, all under your domain and your brand. InstaWP never appears. In WaaS Custom API mode you run your own checkout and keep 100% of the revenue. You own the UI and the login; the API just provisions and operates the sites.
| Client site | Plan | Status |
|---|---|---|
Northwind Studionorthwind.studio |
Growth | Live |
Belle & Co.belleandco.com |
Starter | Live |
Harbor Yogaharboryoga.app |
Growth | Provisioning |
Spin up a real WordPress in CI with one authenticated POST, run your suite against the returned wp_url, then tear it down on merge. It's plain HTTP, no SDK and no CLI required, so the same call works from a GitHub Action, a bash script, or an AI agent that needs a real site to build on, not a mock. The instawp CLI runs on this exact API.
Query your sites with filters like ?type=reserved and page through the results.
Set php_version and wp_version per site at creation.
Pass a configuration_id to apply a saved preset.
instawp login --token and every command runs on this same API.
Tokens scoped to your team and account.
Poll a provisioning site by its task_id until it's ready.
The API isn't an enterprise upsell. The cheapest sandbox and production speak the same endpoints, the same JSON and the same webhooks, so you build your integration against a $2 box and promote it with a plan change. Your cost scales with sites, not seats or an API add-on.
The two real alternatives a builder weighs: roll your own with WP-CLI on servers you manage, or a managed host's API that's usually locked to a top plan and hands back a queue, not a URL.
The API provisions the site. The rest of the platform is what you do with it next. Keep exploring:
Clone, test, push live
SSH, CLI, Git deploy, MCP
Provision sites by API
Save sites & reusable presets
Managed WordPress, per site
Buy, connect, or resell
Bring sites in, free
Connect your stack
Every site, one dashboard
Resell hosting, your brand
Panel for your clients
Sell ready-made sites
One authenticated POST and a real, logged-in WordPress comes back. The API is the on-ramp; reselling and Portal are where it scales.