Application API

Topolo Device Platform

Clear API and contract surface for Topolo Device Platform, grouped under the application instead of split across generic reference sections.

curated No Auth service ID mapped in docs yet

Documentation Map

Authority

Service IDs:

No Auth service ID mapped in docs yet.

Repos: PlatformApplications/TopoloFeed, PlatformApplications/TopoloMDM, PlatformApplications/TopoloDevelopers

Hosts:

https://topolo-feed-api.topolo.app https://topolo-feed-assets.topolo.app https://topolo-feed-analytics-api.topolo.app

Dependencies: topolo-auth, topolo-mdm, topolo-developers

Depends on Topolo Auth: yes

Contract Source

Type: curated

Source: PlatformApplications/TopoloDocs/src/content/public/applications/device-platform.mdx

Source exists: yes

Canonical device-platform coverage lives in the docs application; TopoloFeed contains the feed delivery API, feed asset host, feed operator UI, Android playback runtime, and feed analytics worker. Feed delivery is the callable platform service id `feed` at https://topolo-feed-api.topolo.app, feed media assets are served from the `topolo-feed-assets` R2 bucket at https://topolo-feed-assets.topolo.app, and feed analytics remains a deploy target for device telemetry at https://topolo-feed-analytics-api.topolo.app. TopoloMDM owns device management and Android provisioning. Mobile app catalog metadata belongs to Topolo Developers and is consumed through Developers-owned /api/apps routes. The retained Nodo-origin mobile surfaces are represented there as first-party Topolo Feed, Topolo Provision, and Topolo MDM Mobile records.

API key scopes in Auth catalog: 0

Auth Requirements

No global OpenAPI security scheme is declared.

No API key scopes were found in the checked-in Auth catalog for this service.

Runtime and Deployment

Wrangler surfaces: PlatformApplications/TopoloFeed/AnalyticsAPI/wrangler.toml, PlatformApplications/TopoloFeed/api/wrangler.toml, PlatformApplications/TopoloMDM/topolo-mdm-api/wrangler.toml, PlatformApplications/TopoloMDM/topolo-mdm-console/wrangler.toml, PlatformApplications/TopoloMDM/topolo-provision/wrangler.toml, PlatformApplications/TopoloDevelopers/wrangler.toml

Environment variables: APP_CATALOG_URL, AUTH_API_URL, AUTH_BASE_URL, BROWSER_SERVICE_ID, DEFAULT_TENANT, ENVIRONMENT, FEED_API_URL, RATE_LIMIT_ENABLED, RATE_LIMIT_PERIOD, RATE_LIMIT_REQUESTS, SERVICE_ID, STATE_API_URL

Routes: workers.dev or Pages-only delivery

Observability enabled: yes

README-Derived Interface Surface

Source: PlatformApplications/TopoloMDM/README.md

No route-level highlights were extracted from the current README.

Package Surfaces

topolo-feed-analytics-api

Topolo Feed Analytics API - Analytics collection for digital signage

Source: PlatformApplications/TopoloFeed/AnalyticsAPI/package.json

Scripts: dev, deploy, deploy:dry-run, tail, db:migrate, lint, typecheck, build

topolo-feed-api

Topolo Feed API - Media feed service for digital signage

Source: PlatformApplications/TopoloFeed/api/package.json

Scripts: dev, deploy, deploy:dry-run, tail, lint, typecheck, build

topolo-feed-ui

UI for testing the Topolo Feed API

Source: PlatformApplications/TopoloFeed/ui/package.json

Scripts: build

topolo-mdm-api

State management API for Topolo MDM multi-tenant system

Source: PlatformApplications/TopoloMDM/topolo-mdm-api/package.json

Scripts: dev, deploy, deploy:dry-run, lint, build, test, local-dev, remote-dev, seed-test-data, dev:with-test-data, dev:with-remote

topolo-mdm-console

Topolo MDM Console - Enterprise Device Management

Source: PlatformApplications/TopoloMDM/topolo-mdm-console/package.json

Scripts: dev, build, deploy, lint, preview, astro, typecheck

Runtime Surface

Wrangler surfaces: PlatformApplications/TopoloFeed/AnalyticsAPI/wrangler.toml, PlatformApplications/TopoloFeed/api/wrangler.toml, PlatformApplications/TopoloMDM/topolo-mdm-api/wrangler.toml, PlatformApplications/TopoloMDM/topolo-mdm-console/wrangler.toml, PlatformApplications/TopoloMDM/topolo-provision/wrangler.toml, PlatformApplications/TopoloDevelopers/wrangler.toml

This application does not yet have a source-controlled OpenAPI spec in the docs platform. The current API page is derived from the registered contract source and repository surface.

Failure modes

  • No Auth service ID is registered for this system.