MeloDocsDevelopers
DashboardStatusSupportRequest access
HomeDocumentationAPI referenceChangelog
MELODOCS API

Your data in.
Signed documents out.

The API is opening in stages. Lead intake and MeloScan uploads are live today; drafts, webhooks and payments are on the way — and the finished document is always signed off by a person in the builder.

Start with what’s liveRead the docs

Five minutes

This runs today. Grab a source token from your lead sources and the first POST lands in your pipeline.

# Push a lead into your pipeline — live today
curl -X POST https://melodocs.ai/api/intake/YOUR_SOURCE_TOKEN \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "Dana Whitfield",
    "phone": "(206) 555-0114",
    "notes": "Garage repaint, two coats, prep included"
  }'

# => { "ok": true, "id": "<lead-id>" }

When the draft API ships, the same pattern returns a builder_url — the document opens in the builder for a person to finish, because nothing goes out unsigned-off.

SYNC INLIVELead intakeA POST from any form, site or automation lands a lead in your pipeline.
SYNC INLIVEMeloScan uploadsMeasured rooms from the app — or your own tooling — land in the Scans inbox.
DRAFTSPLANNEDDraft handoffSend a brief and lines, get a builder URL back. A person finishes the document.
EVENTSPLANNEDWebhooksSent, viewed, signed, declined and paid, delivered to your endpoint as they happen.
MONEYPLANNEDPayment linksMeloPay links minted by API, so the deposit collects where the document is.
READPLANNEDDocuments outTotals, the chain of related documents, and a PDF of anything sent.

Deliberately absent: an endpoint that writes and sends a finished document on its own, an embedded editor, and a white label. A quote is a promise about price and scope, so a person signs off.

Lead intake quickstartA lead in your pipeline with one POST — live today.OPEN →How the full API will fitThe shape being built toward, future tense on purpose.OPEN →API referenceEvery live endpoint, documented from the code that runs.OPEN →