campaign family
Updates a campaign's name or a specific section's content, and returns the updated campaign info
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.
curl -X POST https://one.ie/api/ask/campaign:update \
-H "Authorization: Bearer $ONE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"data": { "campaignId": <any>, "content": <any>, "name": <any>, "stageKey": <any> }}'The key is never in a link. npx -y @oneie/cli login writes it to ~/.config/oneie/key on your machine.
Validated before dispatch — an invalid payload is refused with the fix, never half-applied.
campaignId any optional content any optional name any optional stageKey any optional stageName any optional What comes back from the call.
No declared fields.
Every call to campaign:update, counted where it is dispatched — over HTTP or in-process alike. Aggregate only — no actor, no payload, no workspace.
Counting…
Every place in the open source that names campaign:update, 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
Answered by
POST /api/ask/campaign:update, after the envelope
validates the payload.
campaign family · 2 more
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"campaignId": {},
"content": {},
"name": {},
"stageKey": {},
"stageName": {}
},
"additionalProperties": {}
} {
"$schema": "https://json-schema.org/draft/2020-12/schema"
}