Process Session Campaign

Changed on

Read the optimisation-campaign ledger for a cloud-process session.

core exposes it at GET /api/campaign/{session_id} (the ledger the organism workbench renders). The SPA's sessionFetch('/api/campaign/<sid>') becomes /api/processes/<pid>/campaign/<sid> for a process-bound conversation, and this relays it down the process's WS socket via the same _process_rpc bridge as plan/memory/goal. session_id is re-encoded rather than forwarded raw so an id needing escaping can't reshape the core path. A session with no campaign is {"campaign": null} with 200 from core — not an error.

get/api/processes/{process_id}/campaign/{session_id}

Request

  • Base URL: https://api.omicos.cn (the document declares no server; this is the origin it was published from)
  • URL: https://api.omicos.cn/api/processes/{process_id}/campaign/{session_id}
  • Auth: none declared

Path parameters

process_idstring required
session_idstring required

Headers

authorizationstring nullable
x-omicos-devicestring nullable
x-omicos-device-kindstring nullable
x-omicos-device-namestring nullable

Response

Successful Response

object required

Changes

  • ef3006b6f052Revision changes
    • info

      added the new optional header request parameter x-omicos-device

    • info

      added the new optional header request parameter x-omicos-device-kind

    • info

      added the new optional header request parameter x-omicos-device-name