Query fleet-wide edge device status from Litmus Edge Manager using its admin token-based API
domain: api.litmus.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate an admin API token in Litmus Edge Manager's token/API account management screen
Include the token in the X-AuthToken header on requests (Edge Manager uses this instead of OAuth2 bearer tokens used by Litmus Edge itself)
Consult the Litmus API Portal (api.litmus.io) for the specific device/fleet endpoint paths, which are organized by product (Edge, Edge Manager, Unify)
Call the relevant fleet/device endpoints to retrieve connection status, versioning, or deployment state across managed edge devices
Paginate or filter results as needed for large fleets before ingesting into an external monitoring system
Known gotchas
Authentication differs per product surface: Litmus Edge uses OAuth2 client-credentials, Litmus Unify uses OAuth2 password grant, and Edge Manager uses a distinct X-AuthToken — mixing them up causes silent auth failures
Most Edge Manager/Edge endpoints are REST while newer Analytics/Integrations areas in Edge 4.0.x are GraphQL — check which style a given endpoint uses before building a client
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?