Enroll API

POST /api/enroll

JSON body. email and provenance.source are required. sequenceId is an optional UUID — omit it to use the workspace default sequence. Tags merge onto the contact.

curl -s -X POST $APP_URL/api/enroll \
  -H 'content-type: application/json' \
  -H 'x-enrollmill-workspace: you@company.com' \
  -d '{
    "email": "casey@example.com",
    "sequenceId": "11111111-1111-1111-1111-111111111111",
    "tags": ["trial"],
    "provenance": {
      "source": "usagemill.overage",
      "eventId": "evt_01HQ",
      "mill": "usagemill"
    }
  }'

200 returns { ok, enrollmentId, contactId, sequenceId, status, idempotent }. Invalid JSON or payload is 400.

Workspace (no Bearer key in v0)

Auth is soft. There is no API key header yet. Resolution order:

1. Signed-in session cookie, if present.
2. Optional header x-enrollmill-workspace (email). Creates the workspace on first use.
3. Otherwise the first user in the database, or mill@enrollmill.com.

Idempotency

When provenance.eventId is set, retries with the same workspace + event return the existing enrollment and idempotent: true. Without an event id, the key is workspace + email + sequence + source.

Stop on reply or bounce

Webhook stubs accept a payload and record a timeline event. If a matching contact exists, the latest enrollment status becomes replied or bounced — that is the v0 stop. There is no guaranteed inbox and no warmup product.

curl -s -X POST $APP_URL/api/webhooks/bounce \
  -H 'content-type: application/json' \
  -d '{"email":"casey@example.com","reason":"mailbox full"}'

curl -s -X POST $APP_URL/api/webhooks/reply \
  -H 'content-type: application/json' \
  -d '{"email":"casey@example.com","text":"unsubscribe me"}'

Both return { ok: true, recorded: true, contactId, enrollmentId }.

GET /api/health

curl -s $APP_URL/api/health
# {"ok":true}