API

GIVE YOUR SOFTWARE DREAMMAKER.

External systems can submit wants, continue existing missions and receive results — exactly like a person using this interface. Same intake, same continuity, same receipts.

Access is authenticated with a per-node token returned when a mission is created, sent as x-dreammaker-node-token. Requests are rate limited. Missions can only be read by the node that owns them. Responses are JSON.

Live routes

POST /api/public/missions

Live

Open a mission with a stated want, permission snapshot and source channel. Returns a mission ID and a node token for continuity.

GET /api/public/missions/:id

Live

Read persisted mission state, results, attachments, handoffs and payment state. Requires the node token.

POST /api/public/missions/:id/continue

Live

Extend an existing mission with new instruction. Creates a child mission bound to the same node.

POST /api/public/missions/:id/files

Live

Upload context as multipart/form-data. Validated by type and size, stored privately.

POST /api/public/missions/:id/handoff

Live

Request human review, negotiation, approval or execution.

GET /api/public/missions/:id/receipt

Live

Retrieve the manifestation receipt and produced results.

GET /api/public/widget.js

Live

The embeddable DreamMaker widget, submitting into this same mission intake.

Restricted / infrastructure

POST /api/public/integrations/execution/result

Signed

Signed result callback from Damon YLF execution infrastructure. Requires an HMAC signature; unavailable until the result secret is configured.

Organization-level credentials and execution routing are issued directly — contact@damonylf.com.