Sessions and timeouts

A session starts when Axilio allocates a phone. The common customer-visible boundaries are manual release, an optional idle timeout, and the platform’s maximum session duration. Axilio can also close a session when its phone becomes unavailable.

Inspect sessions

Dashboard
CLI
Python SDK
Go SDK
REST API

Open Sessions to filter active and completed sessions. Open a row for its phone, source, workflow, recording, files, live view, and Telemetry.

axilio sessions list --remote
axilio sessions list --history
axilio sessions get sess_123

sessions = client.phones.list_sessions(limit=20)
session = client.phones.get_session("sess_123")

print(session.status, session.phone_id, session.recording_status)

sessions, err := api.Phones.ListSessions(ctx, &platformgo.PhonesListSessionsRequest{
    Limit: platformgo.Int64(20),
})
if err != nil {
    log.Fatal(err)
}

session, err := api.Phones.GetSession(ctx, &platformgo.PhonesGetSessionRequest{
    SessionID: "sess_123",
})
if err != nil {
    log.Fatal(err)
}
fmt.Println(sessions.Total, session.Status, session.PhoneID, session.RecordingStatus)

REST API References:

List sessions: GET /phones/sessions
Get a session: GET /phones/sessions/{session_id}

Examples use Bash. To run them in PowerShell, see Run the curl examples on Windows.

curl --silent --show-error --fail-with-body \
  --url "https://api.axilio.ai/api/v1/phones/sessions?limit=20" \
  --header "X-Axilio-Api-Key: $AXILIO_API_KEY"

curl --silent --show-error --fail-with-body \
  --url https://api.axilio.ai/api/v1/phones/sessions/sess_123 \
  --header "X-Axilio-Api-Key: $AXILIO_API_KEY"

Idle timeout

ttl.idle_timeout_seconds closes a session after that many seconds without a live user connection. A connected control, live-view, or Telemetry viewer keeps the session active; after the last viewer disconnects, the idle clock resumes. A session that was never connected is idle from allocation time. Omit the value, or pass a nonpositive value, for no idle timeout. Positive values are clamped to 1–3,600 seconds. A session without an idle timeout still ends at the one-hour platform cap.

Dashboard
Python SDK
Go SDK
REST API

Open Sessions, click Allocate A Phone, and enter idle timeout (seconds). Leave it blank for no idle timeout.

from axilio import PhoneSessionTtlOptions

allocation = client.phones.allocate(
    phone_type="android",
    phone_id="ph_123",
    ttl=PhoneSessionTtlOptions(idle_timeout_seconds=300),
)

allocation, err := api.Phones.Allocate(ctx, &platformgo.PhoneAllocateRequest{
    PhoneType: platformgo.PhoneAllocateRequestPhoneTypeAndroid,
    PhoneID:   platformgo.String("ph_123"),
    TTL: &platformgo.PhoneSessionTTLOptions{
        IdleTimeoutSeconds: platformgo.Int64(300),
    },
})
if err != nil {
    log.Fatal(err)
}
defer func() {
    if _, err := api.Phones.Deallocate(ctx, &platformgo.PhonesDeallocateRequest{
        PhoneID: allocation.PhoneID,
    }); err != nil {
        log.Printf("release phone: %v", err)
    }
}()

REST API References:

Allocate a phone: POST /phones:allocate

Examples use Bash. To run them in PowerShell, see Run the curl examples on Windows.

curl --silent --show-error --fail-with-body \
  --request POST \
  --url https://api.axilio.ai/api/v1/phones:allocate \
  --header "X-Axilio-Api-Key: $AXILIO_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "phone_type": "android",
    "phone_id": "ph_123",
    "pool": "dedicated",
    "ttl": {
      "idle_timeout_seconds": 300
    }
  }'

The CLI does not currently expose the idle-timeout option. A CLI-started session remains active until you stop it or the maximum duration is reached.

Connection timeout is different

Python’s open_timeout controls how long the SDK waits to connect to the allocated phone. It does not set the session lifetime, wait for an app screen, or change a command deadline:

with client.session("android", phone_id="ph_123", open_timeout=20) as driver:
    print(driver.observe())

Release reliably

Use client.session() when Python owns the whole lifetime. For direct allocations, put deallocation in finally or defer. With the CLI, run axilio sessions stop <session-id> --yes. Closing a Dashboard tab does not release the phone. End the session with Release or Deallocate. Ending a session frees its control lease; it does not erase the dedicated phone’s apps or state and does not end its rental.

Get Started

Phones and Sessions

Workflows and Runs

Files

Observability

Telemetry

Usage

Billing

Organization

Reference

Sessions and timeouts

Inspect sessions

Idle timeout

Connection timeout is different

Release reliably

​Inspect sessions

​Idle timeout

​Connection timeout is different

​Release reliably

Inspect sessions

Idle timeout

Connection timeout is different

Release reliably