THE ROAD AHEAD
How the full API will fit your stack
The shape the API is being built toward — so you can plan an integration before the endpoints exist. Everything on this page is future tense on purpose.
The model is simple: your system pushes data in, a person finishes the document in the MeloDocs builder, and events and results flow back out.
—Push data in — clients, rate-book items and jobs, each carrying your own external id.
—Create a draft — a brief and any explicit lines; the response is a builder URL.
—A person finishes it — the draft opens in the builder, priced from the rate book, and someone signs off before it goes anywhere.
—Events come back — sent, viewed, signed, declined, paid, delivered by webhook.
—Pull the result — totals, the chain of related documents, and a PDF.
One decision is settled: there will be no API that writes and sends a finished document on its own, no embedded editor, and no white label. A quote is a promise about price and scope, so a human signs off. That's the product, not a gap.
Order and timing are not promised here — when an endpoint ships it appears in the reference, documented from what actually runs, and lands in the changelog.
Updated August 6, 2026Did this page help?
NEXTEarly access