Session diagnostics
Inspect session state and client output. The published interface does not define an audit-log API.
Inspect current state
curl --fail-with-body --silent --show-error \
"https://skill.legba.xyz/api/v1/sessions/current" \
-H "Authorization: Bearer $LEGBA_API_KEY"The response contains the current session or null. Inspect its kind, browser, and state before issuing browser actions.
This is a current-state lookup, not a session history. No audit retention period is defined here.
Read client diagnostics
The session client prints results to standard output. Status information and errors go to standard error.
Useful output
| Parameter | Type | Description |
|---|---|---|
start | stdout | SESSION_ID plus PROXY_URL or VIEW_URL when present. These URLs can contain credentials. |
current | stdout | Current session JSON, or null when nothing is running. |
go, read, shot | stderr | Startup retry messages when the browser is not ready. |
read | stderr | The returned page URL and title. |
UPGRADE NEEDED | stderr | A plan refusal and returned explanation. The session client exits with code 4. |
Prepare a useful support report
Record the operation, timestamp, and HTTP status. Include the returned error detail after removing sensitive values. Describe whether the failure occurred during startup or navigation.
Remove API keys and complete session URLs. Page text and screenshots can contain private information too. Share only what the investigation requires.
Check errors and recovery before contacting support. Use Contact us if the issue persists.
Audit-log availability
The published client has no audit-log retrieval endpoint. No event schema, filtering contract, or pagination is documented. Do not assume an organization-level logs API exists.
For your own integration, record non-sensitive operational metadata. Keep that logging separate from Legba's current-session response.