01Run it
Straight from the command's own help.
p202 ltv webhooks create --url https://hooks.example.com/p202 --events revenue.recorded,subscription.changed02What you get
Pick the shape you need. People get a table. Add
--json, --csv or --ndjson for scripts, or -q for ids only. An AI agent gets compact JSON without asking. All output formats03Build your command
Pick values and the command line writes itself, quoted and ready to paste.
p202 ltv webhooks createSet flags below; the command updates as you type.
04Flags
2 flags, plus the global flags every command takes.
| Flag | What it does |
|---|---|
| --eventsstring | Events to send, comma-separated (default every event): customer.updated, revenue.recorded, subscription.changed, conversion.recorded, engagement.recorded, *; comma-separated for severalcustomer.updatedrevenue.recordedsubscription.changedconversion.recordedengagement.recorded* |
| --urlstringrequired | The https endpoint to deliver to (required) |
05How it works
Deliveries are signed: X-P202-Signature is sha256=HMAC-SHA256(body, secret). The secret is in this command's output and nowhere else, ever: store it now. --events chooses what is sent (default every event this version sends; * also takes events later versions add). The URL must be https and must not point at a private, loopback or metadata address.
p202 ltv webhooks create --url https://hooks.example.com/p202 --events revenue.recorded,subscription.changed
06For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands ltv webhooks create --json. - With
AI_AGENT,CLAUDECODEor another agent variable set, output is compact JSON and errors arrive on stderr as a JSON envelope with ahint. - Exit codes: 0 ok, 1 bad input, 2 auth, 3 network, 4 server error, 5 partial failure.
- This command writes and cannot be staged:
--stagedis refused before anything is sent. Have a person run it, or give the agent a key without write scope.
{
"path": "p202 ltv webhooks create",
"use": "create --url https://…",
"short": "Register an endpoint for signed LTV events; the response holds its secret, shown this once",
"long": "Deliveries are signed: X-P202-Signature is sha256=HMAC-SHA256(body, secret). The secret is in\nthis command's output and nowhere else, ever: store it now. --events chooses what is sent\n(default every event this version sends; * also takes events later versions add).\nThe URL must be https and must not point at a private, loopback or metadata address.\n\n p202 ltv webhooks create --url https://hooks.example.com/p202 --events revenue.recorded,subscription.changed",
"runnable": true,
"flags": [
{
"name": "events",
"type": "string",
"default": "",
"usage": "Events to send, comma-separated (default every event): customer.updated, revenue.recorded, subscription.changed, conversion.recorded, engagement.recorded, *; comma-separated for several",
"allowed_values": [
"customer.updated",
"revenue.recorded",
"subscription.changed",
"conversion.recorded",
"engagement.recorded",
"*"
],
"value_list": true,
"required": false
},
{
"name": "url",
"type": "string",
"default": "",
"usage": "The https endpoint to deliver to (required)",
"required": true
}
]
}