WPConvert Developer API
API by WPConvert.ai · rest
The WPConvert Developer API converts a zipped frontend project (static HTML, or a build output from tools such as Lovable, v0, Bolt, Cursor, Replit, or Framer) into an installable WordPress theme. Versioning info.version is the version of this API document, not of the developer tooling. The published CLI (wpconvert) and MCP server (@wpconvert/mcp) are versioned independently; npm lists their current versions. Typical flow 1. GET /api/convert/quota — preflight. Read capabilities.conversion to learn whether a conversion may start and what it will consume. 2. Submit the project: POST /api/convert for archives up to the multipart ceiling, or the signed-upload flow (POST /api/convert/upload-url, an external PUT, then POST /api/convert/from-storage) for larger inputs. 3. Poll GET /api/convert/{jobId}/status until status is done or failed. 4. On success, call GET /api/download/{projectId} for a short-lived signed theme URL, and/or POST…
Endpoint: https://api.wpconvert.ai/
Verification: observed. Source: crawl.
Capabilities (16)
- List every paid option with what it includes and its price
- Start a Stripe Checkout for the option the user chose
- The catalog personalised for this account and theme
- Submit a conversion (multipart upload)
- Submit a conversion from a previously uploaded archive
- Get quota and developer capabilities
- Create a signed upload URL for a large archive
- Get conversion status
- Get a download URL for a completed theme
- Check the MCP access token the hosted MCP server forwards
- Create a one-time upload link
- Check an upload link
- Create a WordPress Playground preview session
- Register an MCP app (dynamic client registration)
- Revoke an MCP access or refresh token
- Get or refresh an MCP access token