Topolo Docs Topolo Platform
Open workspace

Feed

Worked requests, responses, verification and recovery for thirteen public Feed operator actions.

Feed action reference

Discover the exact action and granted target, validate input and inspect the plan before executing. GET workspace console actions can initialize a local mirror. Organization privacy has broader scope than one workspace.

  • Get Feed workspace widget: Return the signed Feed widget contract with device and source counters for its workspace. Missing KV data produces zero counters; this is not proof of enrollment, playback or analytics collection.
  • Summarize Feed impressions: Group impressions by media and event type in the granted workspace, using inclusive millisecond bounds and a SQL LIKE media pattern. The request can initialize the local workspace mirror.
  • Get Feed engagement metrics: Calculate workspace completion, touch interaction and duration metrics by media for inclusive millisecond bounds and a SQL LIKE pattern. Empty results are valid; the request can initialize the local mirror.
  • List observed Feed devices: Return at most 1,000 devices observed in the granted workspace, ordered by most recent observation. Protected device references are decoded, credentials are excluded, and the local mirror may be initialized.
  • Archive empty Feed workspace: Verify that all six Feed data tables are empty for the granted workspace, request canonical archival from Auth, then remove the local identity mirror. The platform decides whether archival is allowed.
  • Generate Feed engagement digest: Persist one workspace digest for a window whose end is greater than its start. Every invocation creates a new digest; configured notification transport is attempted separately and has no delivery receipt in the response.
  • Check Feed completion threshold: Calculate the completion rate for a valid window and persist a new open anomaly only below the requested threshold. A null anomaly with an observed value is a valid HTTP 201 result.
  • Rotate Feed device credential: Replace the credential hash in a protected device assignment in the granted workspace, returning a one-time credential. An unassigned id can receive an assignment; this does not create an observed device row.
  • List registered Feed sources: Read registered sources in the granted workspace, decrypting name and endpoint URL with snake_case status fields. The unpaginated list is ordered by creation and id; the local mirror can be initialized.
  • Register Feed HTTPS source: Store a named HTTPS source in the granted workspace after validating its URL. Registration neither fetches nor imports source content, and every call creates a new record even for a duplicate endpoint.
  • Export Feed organization data: Export all local Feed stores for the authenticated organization, including readable protected fields and per-workspace KV configuration and assignments. This operation is organization-wide and is not limited by a workspace header.
  • Erase Feed organization stores: Erase local Feed organization records and workspace KV data sequentially, then retain a hashed erasure receipt for 2,557 days. Requires exact ERASE confirmation; preserves canonical Auth identity and encryption keys.
  • Record Feed source fetch attempt: Fetch a registered workspace HTTPS source without redirects, consume at most 1,048,576 response bytes, discard the body and persist its terminal attempt. HTTP 200 may contain a failed sync; no content is imported.

Evidence

Actual Feed Worker response using synthetic Auth, workspace grants, in-memory D1/KV and simulated source/notification transport. No live provider, encryption audit, device enrollment or external delivery is established. Credentials are excluded or explicitly redacted. SQL result shapes are also reviewed against migrations and handlers; empty captures do not exercise every populated export store. Live publication and read-back are separate environment evidence.