01Run it
Replace the <placeholders> with your own values, or use the builder below.
p202 forecast-event get <id>02What you get
Captured from the real binary, run against a demo store with 30 days of traffic. Switch tabs to see the same run as JSON, the shape scripts and agents parse.
$ p202 forecast-event get 1 end_date: etag: "f1dad47a8133a438c049115eaf2fefe8295d4dd3" event_date: 2026-11-27 event_id: 1 event_name: Black Friday Weekend expected_impact_pct: 180 impact_type: boost lag_days: 0 lead_days: 0 notes: recurrence: none tags: retail,holiday user_id: 1 version: f1dad47a8133a438c049115eaf2fefe8295d4dd3
$ p202 forecast-event get 1 --json { "data": { "end_date": null, "etag": "\"f1dad47a8133a438c049115eaf2fefe8295d4dd3\"", "event_date": "2026-11-27", "event_id": 1, "event_name": "Black Friday Weekend", "expected_impact_pct": 180, "impact_type": "boost", "lag_days": 0, "lead_days": 0, "notes": null, "recurrence": "none", "tags": "retail,holiday", "user_id": 1, "version": "f1dad47a8133a438c049115eaf2fefe8295d4dd3" } }
03Build your command
Pick values and the command line writes itself, quoted and ready to paste.
p202 forecast-event getSet flags below; the command updates as you type.
04For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands forecast-event get --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.
{
"path": "p202 forecast-event get",
"use": "get <id>",
"short": "Get a forecast-event by ID",
"runnable": true
}