Order a workflow

A workflow is a packaged product — several coordinated steps of real-world work ordered as one unit, under a single escrow lock. Instead of creating and settling each task yourself, you order the workflow, watch its progress, and collect one signed Verified report at the end.

Order it — one escrow lock

Ordering a workflow locks the whole price in escrow atomically, the same way a single task does. The call is mutating, so it needs an Idempotency-Key.

curl -X POST https://api.hannu.africa/v1/workflows \
  -H "Authorization: Bearer $HANNU_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

If the wallet is short, the order fails with insufficient_escrow_balance (402) and nothing is locked. Browse the catalogue and its prices with GET /v1/workflow_products first if you want to confirm the amount before committing.

{
  "data": {
    "workflowId": "wf_5c30",
    "state": "ordered"
  }
}

A successful order emits workflow.ordered. The exact request and response fields are in the OpenAPI document.

Follow the progress

Subscribe to webhooks so your handler learns of each state change without polling — see the event catalogue. If you prefer to poll, read the workflow by id:

curl https://api.hannu.africa/v1/workflows/wf_5c30 \
  -H "Authorization: Bearer $HANNU_KEY"

Download the Verified report

When the workflow completes, its output is a single Verified report — a signed statement of what was checked and found across every step. Request the format you need with ?format=:

curl https://api.hannu.africa/v1/workflows/wf_5c30/report?format=json \
  -H "Authorization: Bearer $HANNU_KEY"

The report is available as json, markdown, html, or attestation (?format=). Use json for a machine-readable report you can file and re-verify, markdown or html to render for a human, and attestation for the signed, portable proof. The report is designed to be filed and independently verified, not eyeballed.