Marketing API

The marketing API follows the same flow as the app: product → strategy → calendar → contents → approvals → reports. All routes are under /v1, accept an API key or an OAuth token, and are scoped by workspaceId (id or slug) in the body / query or by the resource id. Lists return either an array or { items, nextCursor } (noted as paged).

Products

kind is one of APP WEB_SERVICE COMMERCE LOCAL_STORE CREATOR B2B EVENT OTHER; goals[] of INSTALLS SIGNUPS PURCHASES VISITS LEADS FOLLOWERS AWARENESS.

curl https://api.poremu.ai/v1/products \
  -H "Authorization: Bearer $POREMU_API_KEY" -H "Content-Type: application/json" \
  -d '{"workspaceId":"my-workspace","name":"Lumo","kind":"APP","url":"https://lumo.app","goals":["INSTALLS"]}'

Strategy

The analyser needs an LLM: the workspace engine must be CREDITS or BYO_KEY. A workspace in BYO_MCP mode gets 400 VALIDATION_ERROR — there the client does the thinking with analysis_brief → save_strategy over MCP.

Channels, connections & metrics

Connected channels sync daily at 04:00 KST (1 credit per channel to whoever created the connection). Token problems set the connection to NEEDS_REAUTH and fire the connection.needs_reauth webhook.

Calendar

kind is CAMPAIGN PUBLISH LAUNCH REPORT TASK MILESTONE REMINDER; status is planned doing done canceled.

Contents

format: COPY IMAGE VIDEO CAROUSEL POST ARTICLE EMAIL SCRIPT LANDING. status moves IDEA → DRAFT → REVIEW → APPROVED → SCHEDULED → PUBLISHED (or REJECTED / ENDED); publishing to a channel is an approval (PUBLISH_POST). To generate the media itself use Images / Videos and pass generationIds.

Approvals, proposals & rules

action: BUDGET_CHANGE BID_CHANGE PAUSE_RESUME PUBLISH_POST SEND_EMAIL SEND_MESSAGE CREATE_CAMPAIGN UPDATE_CREATIVE WEBHOOK_OUT CUSTOM. Executors exist for BUDGET_CHANGE ({ level: "campaign" | "adset", externalId, dailyBudgetKrw }) and PAUSE_RESUME ({ level, externalId, status: "PAUSED" | "ACTIVE" }) on Meta Ads, Google Ads and Naver Search Ads (2 credits per execution), and for WEBHOOK_OUT. evidence is { dataSnapshot?, rule?, expectedEffect?, risks?, reversible?, notes? } — fill it so the approver can decide at a glance.

curl https://api.poremu.ai/v1/approvals \
  -H "Authorization: Bearer $POREMU_API_KEY" -H "Content-Type: application/json" \
  -d '{
    "workspaceId": "my-workspace",
    "productId": "PRODUCT_ID",
    "channelId": "CHANNEL_ID",
    "action": "BUDGET_CHANGE",
    "summary": "Cut Meta daily budget ₩120,000 → ₩96,000 (CPA ₩11,400 > target ₩9,000)",
    "payload": { "level": "campaign", "externalId": "2384…", "dailyBudgetKrw": 96000 },
    "evidence": { "expectedEffect": { "metric": "cpa", "from": 11400, "to": 9500 }, "reversible": true }
  }'

Approval lifecycle events (approval.requested, approval.decided, approval.executed) are delivered as webhooks.

Reports

For anything richer than a scheduled report — conditions, AI runs, Slack, email with templated text — build an automation.

AI marketer (agent)

The agent uses the same tools listed on the MCP page. In BYO_MCP mode /agent/chat answers 400 VALIDATION_ERROR — use the assistant you connected instead.

const res = await fetch('https://api.poremu.ai/v1/agent/chat', {
  method: 'POST',
  headers: { Authorization: `Bearer ${process.env.POREMU_API_KEY}`, 'Content-Type': 'application/json', Accept: 'text/event-stream' },
  body: JSON.stringify({ workspaceId: 'my-workspace', productId, message: 'Which channel should get more budget next week, and why?' }),
});
for await (const chunk of res.body) process.stdout.write(new TextDecoder().decode(chunk)); // event: delta / tool / approval / done

Inbound hooks

To push your own events — orders, sign-ups, metric rows — into a product, create an inbound hook (POST /v1/hooks) and POST to its token URL. Details in Webhooks → Inbound hooks.

Errors & limits

The usual error envelope applies. Marketing-specific cases: