---
title: "Get computer entity sessions"
method: GET
path: "/api/v2/computers/{object_id}/sessions"
tags: ["Computers", "Community", "Enterprise"]
---

# Get computer entity sessions

`GET /api/v2/computers/{object_id}/sessions`

Get a list, graph, or count of the principals with active sessions on this computer.

## Query parameters

- `skip` integer
- `limit` integer
- `type` 'list' | 'graph'
- `sort_by` string — Sort by column. Can be used multiple times; prepend a hyphen for descending order. See parameter description for details about which columns are sortable.

## Response `200`

**OK**

This endpoint returns a response, dependent upon which return type is requested by the `type` parameter.
The only supported `type` parameter is `list`.
While `list` is the only supported `type` parameter, the `graph` parameter can be used
and will result in a different response structure then documented here.
For those interested in using the undocumented graph type parameter, the response type is described in the schema
`model.bh-graph.graph`.

- object
  - `count` integer — The total number of results.
  - `skip` integer — The number of items to skip in a paginated response.
  - `limit` integer — The limit of results requested by the client.
  - `data` object[]
    - `objectID` string
    - `name` string
    - `label` string
    - `kinds` string[]

## Other responses

- `400` — **Bad Request** This could be due to one of the following reasons: - JSON payload is missing or malformed - Path or query parameters are missing or invalid/malformed - The data sent is not valid (ex- sending a `string` in an `integer` field)
- `401` — **Unauthorized** This endpoint failed an authentication requirement. Either the client tried to access a protected endpoint without being authenticated, or an auth validation failed (ex- invalid credentials or expired token).
- `403` — **Forbidden** This is most commonly caused by an authenticated client trying to access a resource that it does not have permission for.
- `429` — **Too Many Requests** The client has sent too many requests within a certain time window and tripped the rate limiting middleware.
- `500` — **Internal Server Error** This is usually the result of either an unexpected database or application error. The client may try modifying or resending the request, but the error is likely not related to the client doing something wrong.

---

[API](https://skmtc.net/specterops/apis/bloodhound-api.md) · [All operations](https://skmtc.net/specterops/apis/bloodhound-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/specterops/bloodhound-api/versions/9e5dcb1a1b37/schema)