Site menu

Developers

Build on MakeMySiteLive

Everything you can do in the dashboard, you can do in code. Drive deploys from a public REST API, or let an AI agent do it through our hosted MCP server.

REST API

Base URL https://www.makemysitelive.com. Authenticate every request with a scoped key: Authorization: Bearer mmsl_…

POSTCreate a site
curl -X POST https://www.makemysitelive.com/v1/sites \
  -H "Authorization: Bearer mmsl_your_key" \
  -H "Content-Type: application/json" \
  -d '{"subdomain":"my-site","name":"My Site"}'

POSTDeploy a ZIP
curl -X POST https://www.makemysitelive.com/v1/sites/SITE_ID/deploy \
  -H "Authorization: Bearer mmsl_your_key" \
  -H "Content-Type: application/zip" \
  -H "X-File-Name: site.zip" \
  --data-binary @site.zip

POSTDeploy a large ZIP in the background
# A large ZIP can outlast a proxy's timeout. Ask for a background deploy:
curl -X POST "https://www.makemysitelive.com/v1/sites/SITE_ID/deploy?async=true" \
  -H "Authorization: Bearer mmsl_your_key" \
  -H "Content-Type: application/zip" \
  -H "X-File-Name: site.zip" \
  --data-binary @site.zip
# 202 {"status":"processing","deployId":"…","statusUrl":"/v1/sites/SITE_ID/deploys/…"}

# Poll until status is "succeeded" or "failed":
curl https://www.makemysitelive.com/v1/sites/SITE_ID/deploys/DEPLOY_ID \
  -H "Authorization: Bearer mmsl_your_key"

POSTPublish a microsite from HTML
curl -X POST https://www.makemysitelive.com/v1/microsites \
  -H "Authorization: Bearer mmsl_your_key" \
  -H "Content-Type: application/json" \
  -d '{"subdomain":"my-page","name":"My Page","html":"<!doctype html><h1>Live</h1>"}'

Endpoints
MethodEndpointWhat it doesScope
GET/v1/meYour accountaccount:read
GET/v1/sitesList full sitessites:read
GET/v1/sites/{id}Site + version historysites:read
GET/v1/check-subdomain?name=Check availabilitysites:read
POST/v1/sitesCreate a full sitesites:write
POST/v1/sites/{id}/deployDeploy a ZIP (raw body). Add ?async=true to run it in the backgroundsites:write
GET/v1/sites/{id}/deploys/{deployId}Progress of a background deploysites:read
POST/v1/sites/{id}/rollbackRoll back to a versionsites:write
PATCH/v1/sites/{id}/protectionPassword protection (paid)sites:write
POST/v1/sites/{id}/tierSwitch FREE / PAIDsites:write
POST/v1/sites/{id}/subdomainRename the subdomainsites:write
DELETE/v1/sites/{id}Delete a sitesites:delete
GET/v1/micrositesList micrositessites:read
GET/v1/microsites/{id}Microsite + versionsites:read
POST/v1/micrositesCreate & publish from HTMLsites:write
POST/v1/microsites/{id}/deploy-htmlRepublish microsite HTMLsites:write

API key scopes (least privilege)

account:read
View account details
sites:read
List and inspect sites
sites:write
Create, deploy, roll back, rename, protect
sites:delete
Permanently delete sites

Start building

Create a free account, generate a key, and deploy your first site from code.

Create your free account

Publishing limits

To keep the service fair, each account and each IP address can publish a limited number of times a day.

  • Each account can deploy 10 times in 24 hours, or 50 times when you deploy to a paid site. Dashboard uploads, REST API deploys, MCP updates and upload links all count toward the same total, for full sites and microsites alike.
  • Each IP address can also deploy to free sites 10 times in 24 hours, and to paid sites 100 times, however many accounts use it.
  • Only successful uploads use up your allowance, including submissions saved for review. An upload that is rejected, such as a ZIP without an index.html, does not.
  • Creating a new microsite through the dashboard or REST API has its own limit: 5 a day per IP address. It does not use up your deploys.
  • New accounts get 2 free microsites. When all are used, creating another answers 403 with a link to add a microsite slot ($1 a month or $10 a year each). Older accounts keep the allowance they have. A publish that is rejected on the first try does not keep a slot.
  • If you hit a limit, the API answers 429 with a Retry-After header and a message saying which limit you reached. The header is the number of seconds left before you can try again. Wait that long, then retry.
  • Deploy when your content changes, not on a timer. A script that republishes a live page every few minutes will use up the day's deploys quickly.

MCP server

Connect an MCP-capable AI client (like Claude) to our hosted server and an agent can create, deploy, roll back, and protect your sites by chatting, within your plan.

Add it as a remote connector in your client and sign in with your MakeMySiteLive account (OAuth). Grant read-only or read-write access. The agent acts only as you. It exposes read tools (account, list, inspect, check-subdomain) and, with write access, create / deploy / rollback / password-protection / delete.

Read the MCP guide →
Server URLhttps://mcp.makemysitelive.com/mcp

Start building

Create a free account, generate a key, and deploy your first site from code.