Tensorlake Documentation

SSH status

curl --request GET \
  --url https://{identifier}.sandbox.tensorlake.ai/api/v1/ssh/status \
  --header 'Authorization: Bearer <token>'

{
  "enabled": true,
  "pid": 123,
  "host_key_fingerprint": "<string>"
}

GET

api

ssh

status

SSH status

curl --request GET \
  --url https://{identifier}.sandbox.tensorlake.ai/api/v1/ssh/status \
  --header 'Authorization: Bearer <token>'

{
  "enabled": true,
  "pid": 123,
  "host_key_fingerprint": "<string>"
}

Get the sandbox’s internal SSH server status.

This endpoint reports the in-sandbox sshd lifecycle used by Tensorlake’s SSH proxy. To connect with SSH as an end user, see SSH and PTY Sessions.

The public sandbox proxy authenticates your API key and injects the internal forwarded-auth headers required by the daemon.

Endpoint

GET /api/v1/ssh/status

curl https://<sandbox-id>.sandbox.tensorlake.ai/api/v1/ssh/status \
  -H "Authorization: Bearer $TENSORLAKE_API_KEY"

Tensorlake returns 200 OK:

{
  "enabled": true,
  "pid": 123,
  "host_key_fingerprint": "SHA256:..."
}

Authorization

string

header

required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

SSH daemon status

enabled

boolean

required

pid

integer<int32> | null

host_key_fingerprint

string | null

⌘I