Build with Mondovo

Creates a site from a structured brief and starts generation in the background (~60s). Returns 202 immediately — poll the site until status is ready. Pass an idempotency_key so a retried timeout returns the original site instead of creating a duplicate.

curl -X POST https://app.mondovo.com/api/v1/sites \
  -H "Authorization: Bearer mk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Bright Path Physio",
    "business": {
      "industry": "physiotherapy",
      "location": "Austin, TX",
      "description": "Sports injury and rehab clinic."
    },
    "design": { "style": "clean, modern", "color_palette": { "primary": "#0f766e" } },
    "goal": "book an appointment",
    "idempotency_key": "3f9d2c1a-7e54-4b0e-9a1f-2b6c8d0e4f5a"
  }'

HTTP/1.1 202 Accepted
{
  "site_id": "5f8a1c2e-1234-4b6f-9d3e-0a1b2c3d4e5f",
  "status": "generating",
  "estimated_seconds": 60,
  "poll_url": "/api/v1/sites/5f8a1c2e-1234-4b6f-9d3e-0a1b2c3d4e5f"
}

Lists your organization’s sites, most recent first (up to 50).

curl https://app.mondovo.com/api/v1/sites \
  -H "Authorization: Bearer mk_live_..."

HTTP/1.1 200 OK
{
  "sites": [
    {
      "site_id": "5f8a1c2e-1234-4b6f-9d3e-0a1b2c3d4e5f",
      "name": "Bright Path Physio",
      "status": "ready",
      "preview_url": "https://app.mondovo.com/preview/abc123",
      "pages": ["/", "/about", "/contact"],
      "created_at": "2026-07-24T10:00:00Z"
    }
  ],
  "total": 1
}

Returns status, generation progress, a shareable preview_url, an editor_url, the live deployment_url once published, and page slugs. Use this to poll while status is generating or publishing.

curl https://app.mondovo.com/api/v1/sites/5f8a1c2e-... \
  -H "Authorization: Bearer mk_live_..."

Applies an AI edit to one page (page defaults to the homepage). Counts against your monthly AI-edit allowance; if the change can’t be saved, no allowance is consumed.

curl -X POST https://app.mondovo.com/api/v1/sites/5f8a1c2e-.../refine \
  -H "Authorization: Bearer mk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "instruction": "Make the hero headline more confident and add a FAQ section", "page": "/" }'

HTTP/1.1 200 OK
{
  "site_id": "5f8a1c2e-1234-4b6f-9d3e-0a1b2c3d4e5f",
  "status": "refined",
  "message": "Site has been refined successfully.",
  "poll_url": "/api/v1/sites/5f8a1c2e-1234-4b6f-9d3e-0a1b2c3d4e5f"
}

Deploys the site to its platform address (e.g. https://<subdomain>.mondovo.com; the exact URL comes back as deployment_url). Custom domains attach in the dashboard. If the site still carries AI-generated placeholder contact details you’ll get a 422 — fix them via refine, or resend with confirm_contact_info: true. See billing notes for the first-publish 402.

curl -X POST https://app.mondovo.com/api/v1/sites/5f8a1c2e-.../publish \
  -H "Authorization: Bearer mk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "subdomain": "bright-path-physio" }'

HTTP/1.1 200 OK
{
  "site_id": "5f8a1c2e-1234-4b6f-9d3e-0a1b2c3d4e5f",
  "status": "published",
  "deployment_url": "https://bright-path-physio.mondovo.com",
  "message": "Site published successfully."
}

Pass any HTTPS URL — including an expiring signed URL — and Mondovo downloads the file, stores it permanently on our CDN, adds it to the site’s asset library, and returns a stable URL. Images (JPG/PNG/WebP/GIF, max 20 MB) and video (MP4/WebM/MOV, max 80 MB; optimized for the web after upload).

curl -X POST https://app.mondovo.com/api/v1/sites/5f8a1c2e-.../assets \
  -H "Authorization: Bearer mk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "url": "https://example.com/clinic-hero.jpg", "alt_text": "Clinic reception" }'

HTTP/1.1 200 OK
{
  "site_id": "5f8a1c2e-1234-4b6f-9d3e-0a1b2c3d4e5f",
  "asset_id": "9c2d4e6f-...",
  "url": "https://site-assets.mondovo.com/sites/5f8a1c2e-.../uploads/aB3xY9....jpg",
  "type": "image",
  "mime_type": "image/jpeg",
  "bytes": 482113,
  "message": "Stored the image permanently. Use the returned url — it will not expire."
}

Soft-deletes a draft site. Published sites can’t be deleted via the API — unpublish first from the dashboard.

curl -X DELETE https://app.mondovo.com/api/v1/sites/5f8a1c2e-... \
  -H "Authorization: Bearer mk_live_..."

HTTP/1.1 200 OK
{ "deleted": true, "site_id": "5f8a1c2e-1234-4b6f-9d3e-0a1b2c3d4e5f" }

Create-or-update up to 500 contacts per call. Each one is matched against the site’s existing contacts on match_on (email by default, matched case-insensitively): a match is updated, everything else is created — so re-sending the same batch is safe, and paging a large import is safe.

Any attribute the CRM has no column for goes in custom_fields as flat key/value pairs. Each new key is declared as a filterable field automatically, so imported attributes are immediately usable in filters and segments. Tags merge with whatever the contact already carries unless you pass tags_mode: "replace".

Send dry_run: true first to see the counts without writing anything.

curl -X POST https://app.mondovo.com/api/v1/sites/5f8a1c2e-.../contacts \
  -H "Authorization: Bearer mk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "match_on": "email",
    "tags_mode": "merge",
    "contacts": [
      {
        "email": "ann@example.com",
        "first_name": "Ann",
        "last_name": "Okafor",
        "company": "Okafor Dental",
        "phone": "+1 512 555 0143",
        "tags": ["newsletter", "2026-import"],
        "custom_fields": { "plan": "gold", "seats": 12, "renewal_date": "2027-03-01" }
      },
      { "email": "bo@example.com", "first_name": "Bo", "tags": ["2026-import"] }
    ]
  }'

HTTP/1.1 200 OK
{
  "site_id": "5f8a1c2e-1234-4b6f-9d3e-0a1b2c3d4e5f",
  "created": 1,
  "updated": 1,
  "total_submitted": 2,
  "duplicates_in_batch": 0,
  "stage_changes_ignored": 0,
  "fields_defined": ["plan", "seats", "renewal_date"],
  "matched_on": "email",
  "tags_mode": "merge",
  "message": "Imported 1 new and updated 1 existing contact(s)."
}

Two limits worth knowing before you plan a migration: status (the pipeline stage) is applied to new contacts only — an import never moves an existing contact along your pipeline, because that would fire your automations in bulk — and no endpoint here deletes a contact.

A site can hold only one contact per email address (compared without regard to case), enforced by the database rather than by a check this endpoint runs — so parallel imports cannot race each other into duplicates. If a contact appears mid-batch it is updated rather than rejected. Matching on phone has no such guarantee, because different people legitimately share a phone number; match on email when it has to be exact.

Returns contacts with their tags and custom fields, newest first. Filter with status, search (name/email/company), tags (comma-separated; a contact must carry every tag listed), acquisition_source, acquisition_campaign, created_after and created_before. Paginate with limit (max 200) and offset; total counts everything matching the filter, not the page.

curl "https://app.mondovo.com/api/v1/sites/5f8a1c2e-.../contacts?tags=newsletter&limit=50" \
  -H "Authorization: Bearer mk_live_..."

HTTP/1.1 200 OK
{
  "site_id": "5f8a1c2e-1234-4b6f-9d3e-0a1b2c3d4e5f",
  "total": 412,
  "limit": 50,
  "offset": 0,
  "contacts": [
    {
      "id": "9c2d4e6f-...",
      "email": "ann@example.com",
      "first_name": "Ann",
      "company": "Okafor Dental",
      "status": "qualified",
      "tags": ["newsletter", "2026-import"],
      "custom_fields": { "plan": "gold" },
      "lead_score": 80,
      "created_at": "2026-09-01T10:22:31.000Z"
    }
  ]
}

Returns a single contact with every stored attribute.

curl https://app.mondovo.com/api/v1/sites/5f8a1c2e-.../contacts/9c2d4e6f-... \
  -H "Authorization: Bearer mk_live_..."

Applies tag additions and removals across a set of contacts in one call. Both are applied to each contact’s existing tags, so tags you don’t mention survive. Tags are what segments filter on, so this changes who is in a saved segment.

curl -X POST https://app.mondovo.com/api/v1/sites/5f8a1c2e-.../contacts/tags \
  -H "Authorization: Bearer mk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "contact_ids": ["9c2d4e6f-...", "1a2b3c4d-..."], "add": ["campaign-sep"], "remove": ["cold"] }'

Returns the custom attributes defined on this site’s contacts and the pipeline stage keys status will accept. Call it before an import to map your columns onto the vocabulary the site already uses instead of creating near-duplicates.

HTTP/1.1 200 OK
{
  "site_id": "5f8a1c2e-1234-4b6f-9d3e-0a1b2c3d4e5f",
  "fields": [
    { "field_key": "plan", "label": "Plan", "field_type": "text", "options": [] }
  ],
  "stages": [
    { "key": "new", "label": "New" },
    { "key": "qualified", "label": "Qualified" }
  ],
  "stages_source": "default"
}

Declare an attribute so it gets a proper label and type instead of rendering as a raw key. Only needed when you want a specific label or a non-text type — the import creates a plain text field for any new key it sees. Defining a field never changes existing contact values.

curl -X POST https://app.mondovo.com/api/v1/sites/5f8a1c2e-.../contacts/fields \
  -H "Authorization: Bearer mk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "field_key": "plan", "label": "Plan", "field_type": "select", "options": ["gold", "silver"] }'