---
title: "GET /{stack}/adminconfig/v2/status"
method: GET
path: "/{stack}/adminconfig/v2/status"
tags: ["system"]
---

# GET /{stack}/adminconfig/v2/status

`GET /{stack}/adminconfig/v2/status`

describe the generic information about the stack

## Path parameters

- `stack` string, required

## Response `200`

stack information: status, type, version

- object
  - `status` StackStatus
    - `infrastructure` object, required
      - `stackType` string — the type of the stack (Victoria/Classic)
      - `stackVersion` string — the version of the stack
      - `status` string — the status of the infrastructure 1) Ready - The stack is ready, and infrastructure is up to date. 2) Pending - The stack has some pending changes that haven't been applied to the stack yet. The changes could be internal system changes for stacks or user requested changes like modification to allow lists. 3) Failed - There were some errors while applying changes to the stacks were being applied. The changes could be internal system changes for stacks or user requested changes like modification to allow lists. User should reach out to Splunk support for resolution.
    - `messages` object, required
      - `restartRequired` boolean — The stack has a notification to restart splunk server. User should restart stack via UI for all configurations to be completed. It may take some time for the correct state for restart-required field to be populated in a Search Head Cluster, given sync delays with different Search Heads

## Other responses

- `default` — unexpected error

---

[API](https://skmtc.dev/splunk/apis/splunk-cloud-admin-api.md) · [All operations](https://skmtc.dev/splunk/apis/splunk-cloud-admin-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/splunk/splunk-cloud-admin-api/revisions/65903649d1c2/schema)