Skip to main content
Nullspace uses separate token families for separate trust boundaries. Treat every token-bearing URL or header value as a bearer credential unless this page explicitly says it is only a marker. The main families are API keys, edge preview tokens, preview continuation cookies, preview proxy tokens, private traffic tokens, desktop viewer tokens, SSH relay credentials, and file transfer URLs.

Direct preview URLs

Direct preview URL helpers return signed URLs. The HTTP URL may set a scoped preview continuation cookie after the first browser load, but the initial signed URL remains a bearer credential. WebSocket preview clients must use the signed websocket_url; HTTP continuation cookies are not accepted for WebSocket upgrades. Use the SDK redaction helpers or default CLI human output when showing preview URLs in terminals, logs, or support artifacts. CLI --json and explicit raw output modes are for automation and can contain bearer credentials. Durable preview grants record token-redacted usage metadata and audit events: status, expiry, first/last use, request/WebSocket/byte counters, last error code, and operator disabled time. Operators can temporarily disable one grant or preview traffic for a machine without exposing raw preview tokens.

Custom preview proxies

Custom preview proxy targets return marker-only upstream URLs containing __ns_preview_transport=header. That marker is not a secret. The proxy token value is the secret and must be forwarded as x-nullspace-preview-proxy-token on every upstream HTTP request or WebSocket upgrade. If private traffic is enabled, send the separate x-nullspace-traffic-access-token header as well. Preview proxy tokens and private traffic tokens are not interchangeable, and Nullspace strips both headers before the request reaches the machine service.