checkout:resume

checkout family

Wake a run suspended at a `sell` step — the storefront webhook fires this on checkout.session.completed with the (runId, stepId) it stamped at create. Sibling of human:resolve.

Effect: signal; Fire-and-forget — the call returns once accepted, not once done.
Caller: manage_workflows; The class of authority the caller must already hold, decided from the attested context with no round trip.
Cost: free; What one call costs, so you can budget before acting.
Reversible: yes; The effect can be undone by a later call.
Idempotent: yes; Safe to retry as-is.

Send it with your agent

One click hands your coding agent a prompt that registers the substrate, reads this contract, and makes the call. Launch opens the app; the others copy the prompt.

Claude Code

Codex

Cursor

Gemini CLI

Claude Desktop

ChatGPT

curl -X POST https://one.ie/api/signal/checkout:resume \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "runId": "run_1", "stepId": "s2", "slug": "acme" }}'

The key is never in a link. npx -y @oneie/cli login writes it to ~/.config/oneie/key on your machine.

Request

Validated before dispatch — an invalid payload is refused with the fix, never half-applied.

runId string required
stepId string required
slug string optional

Response

The acknowledgement shape — the work itself completes after the call returns.

ok boolean
status string
error string

Traffic

Every call to checkout:resume, counted where it is dispatched — over HTTP or in-process alike. Aggregate only — no actor, no payload, no workspace.

Counting…

Wiring

Every place in the open source that names checkout:resume, and the file that answers it. Read from the tree at build time — a receiver is reached by NAME through one door, so there is no import edge to follow and a grep is the honest shape of the question. Structure, not volume — the count is in Traffic above.

Called from

API route 2

one.ie/web/src/lib/bind-receiver.ts:129
one.ie/web/src/pages/api/storefront/webhook.ts:128

Workflow 2

one.ie/web/src/components/workflows/step-visual.ts:319
one.ie/web/src/lib/workflow-receivers.ts:237

Docs 1

one.ie/web/src/content/docs/workflows.md:97

→

Answered by

checkout:resume one.ie/web/src/lib/workflow-receivers.ts:1826 Dispatched through POST /api/signal/checkout:resume, after the envelope validates the payload.

checkout family · 1 more

checkout:create

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "runId": {
      "type": "string"
    },
    "stepId": {
      "type": "string"
    },
    "slug": {
      "type": "string"
    }
  },
  "required": [
    "runId",
    "stepId"
  ]
}

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "status": {
      "type": "string"
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}