Authenticate and pull reality capture site data from NavVis IVION via its REST API
domain: knowledge.navvis.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm your IVION license tier includes REST API access (Professional or Enterprise)
Request a login mandate via /api/auth/mandate/request, or generate tokens directly via /api/auth/generate_tokens
Store the returned access token (a short-lived JWT) and refresh token, refreshing the access token before it expires
Call REST endpoints (e.g., site/dataset listing, user/permission management) using the access token for authorization
For UI-embedded customization instead of data access, use the separate Frontend API rather than the REST API
Known gotchas
Authentication changed in August 2022 from a single long-lived token to a refreshable access/refresh token pair — older examples using a single static token are outdated
REST API and Frontend API are two distinct APIs for different purposes (data access vs UI customization) — don't expect feature parity between them
REST API access is gated by IVION license tier (Professional/Enterprise) and isn't available on lower tiers
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?