API ReferenceOverview

API Reference

The V1 API is 8 endpoints. Base URL: https://api.warpweb.ai.

All requests require Bearer authentication. All bodies are JSON.

Endpoints

MethodPathPurpose
POST/v1/sitesCreate a new site (research + build + deploy).
GET/v1/sitesList your sites.
GET/v1/sites/:idGet a site’s status and metadata.
POST/v1/sites/:id/revisionsRequest a revision (patch or rewrite).
POST/v1/sites/:id/domainsAttach a domain you already own.
POST/v1/domains/checkCheck domain availability and price.
POST/v1/domains/registerBuy a new domain and auto-attach.
POST/v1/sites/:id/webhooks/formsConfigure the form-submission webhook URL.

Common conventions

IDs. Site IDs look like site_<uuid>. Always treat them as opaque strings.

Timestamps. ISO 8601 UTC, e.g. 2026-05-17T14:23:11Z.

Pagination. List endpoints accept limit (default 50, max 200) and cursor (opaque). The response includes next_cursor when more pages exist.

Errors. Non-2xx responses return JSON with a stable error code and a human-readable message:

{
  "error": "site_not_found",
  "message": "No site with id site_abc123 belongs to your account."
}
StatusMeaning
400Malformed request body or invalid parameters.
401Missing or invalid API key.
403Authenticated but not authorized for this resource.
404Resource not found, or endpoint not part of V1 scope.
409Conflict (e.g. domain already attached to another site).
422Validation failed (e.g. unprocessable business description).
429Rate limit exceeded. See Authentication → Rate limits.
5xxWarpweb-side error. Safe to retry with exponential backoff.

Credit-eligible operations deduct from your balance on success. Failed operations don’t charge. See Pricing & Credits for the cost table.

Not in V1

These endpoints are deferred to V1.5 and currently return 404 endpoint_not_in_v1_scope:

  • GET /v1/sites/:id/research — read the research artifact
  • POST /v1/sites/:id/research/approve — explicit research approval
  • POST /v1/sites/:id/research/reject — reject research and restart

For V1, POST /v1/sites auto-approves the research step and proceeds straight to build. The human-in-the-loop research workflow lands when there’s customer pull for it.