keitaro-flowslisted

# Keitaro Flow Management ## Process 1. Read `keitaro/references/keitaro-api.md` for stream endpoint details 2. Read `keitaro/references/flow-patterns.md` for common patterns 3. Parse user intent and context 4. Execute API calls 5. Display result ## Create Flow When user describes a flow setup: 1. Identify the pattern (see `references/flow-patterns.md`): - White + Offer (cloaking) - A/B test - GEO split - Device split - Direct offer 2. Determine required fields: - Campaign ID (required) - Type: regular, forced, or default - Schema: redirect, landings, offers, or landings_offers - Weight (for A/B testing) - Filters (geo, device, OS, etc.) - Landing page IDs - Offer IDs 3. Create via API ### Quick Patterns **"Add white page to campaign 12":** Endpoint: `POST /streams` (NOT PUT — Keitaro uses POST for both create and update) ```json { "campaign_id": 12, "type": "default", "name": "White Page", "action_type": "show_landing_page", "schema": "landings", "landings": [{"id": <white_landing_id>}] } ``` **"Add offer flow for DE desktop":** Endpoint: `POST /streams` ```json { "campaign_id": 12, "type": "regular", "name": "DE Desktop", "action_type": "redirect", "weight": 100, "schema": "landings_offers", "filters": [ {"name": "geo", "mode": "accept", "payload": "DE"}, {"name": "device_type", "mode": "accept", "payload": "desktop"} ], "landings": [{"id": 5}, {"id": 6}], "offers": [{"id": 10}] } ``` **Upd