Fleet software-inventory coverage for a project's instances.

GET

/v1/projects/{projectId}/inventory/instances

Code sample: Shell / cURL

curl --request GET \
  --url https://stratum.example.com/v1/projects/example/inventory/instances \
  --header 'Authorization: Bearer <token>'

• A Stratum cluster endpoint.

. One summary per live instance with a coverage signal (reporting / stale / absent) derived from the agent’s last report, so non-reporting instances are surfaced rather than hidden.

Authorizations

• bearerAuth

Parameters

Path Parameters

projectId

required

string

/^p-[a-z0-9-]+$/

Responses

200

Per-instance inventory summaries.

Media typeapplication/json

object

items

required

Array<object>

object

instanceId

required

string

os

string

kernel

string

agentVersion

string

coverage

required

Per-instance reporting health: reporting = fresh; stale = was reporting but has gone quiet; absent = never reported (or a terminated/agentless guest).

string

Allowed values: reporting stale absent

lastSeen

string format: date-time

collectedAt

string format: date-time

Example

{
  "items": [
    {
      "coverage": "reporting"
    }
  ]
}

403

Authenticated but not authorized.

Media typeapplication/problem+json

object

type

required

string format: uri

title

required

string

status

required

integer

>= 400 <= 599

detail

string

instance

string format: uri-reference

requestId

required

string

code

required

string

issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object

code

required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string

statement

required

Index of the statement at fault; -1 for the document as a whole.

integer

>= -1

detail

required

string

action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string

errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object

field

required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string

message

required

string

details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object

key

additional properties

any

Example

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}